An app or an agent deleted by mistake, rename, publish and clone errors in My Apps, settings that will not save, automations that fail or pause, notifications that do not come, where form answers go, and a site that is slow or looks wrong on a phone.
This page covers the screens around your apps: the My Apps list, the Studio settings, automations and notifications. Most messages here mean one action did not finish, and trying again is safe. Start with the first section if you deleted something by mistake. To find a screen, see Where is everything.
An app. The Delete application window warns "This action is irreversible". There is no recycle bin you can open yourself. The Saved Versions of a deleted app are kept for 6 months, so open a ticket right away with the app name and the time you deleted it, and the team will check what can be brought back. Next time, if you only want the app off the internet, open Publication status on the app card and choose Not published. To keep a copy before a big change, use Duplicate.
An agent. Agents are not deleted, they are archived. 🗄️ Move to archive asks "Move the agent to the archive? It will stop being active and will not appear in the regular list. All data is kept and you can restore it at any time." To bring one back, open 🗄️ Archive at the bottom of the agents list and click ♻️ Restore. You see "The agent was restored and is active again".
Delete a test app safely: Before deleting, open the app once more and check it is the one you mean: two apps can have similar names. The app you have open now cannot be deleted from the list.
You see | What it means | What to do
"Could not rename app" | The new name was not saved. | Try again. Use a name that is not empty.
"Could not publish app" or "Could not unpublish app" | Changing the publication status did not finish. | Try again from Publication status, or publish from inside the Studio. See The live site is not updating.
"Clone failed" | The copy of the app was not created. | Try again in a moment. Your original app is not affected.
"Build status is temporarily unavailable. Reopen the app to reconnect." | The list lost track of a build that is running. | Open the app; the build may still be running.
"The action could not be completed. Please try again." | A request from this screen did not go through. | Reload the page and try again.
"Favorites could not be loaded. Refresh to try again." | The starred apps did not load. | Click Refresh.
"The favorite change was not saved. Please try again." | The star was not saved. | Click the star again.
You see | What it means | What to do
"Could not save. Try again." | A setting was not saved, usually a dropped connection. | Click save again. Nothing else changed.
"We could not load this screen." | A settings screen did not load. | Click Refresh, or reload the page.
"Could not delete. Try again." | Deleting an item did not finish. | Try again. The item is still there.
"The action did not work." | An action on the Users screen did not finish. | Try again. See My customers cannot sign in.
"Could not save or load this setting. Please try again." | The Page loading acceleration setting did not save. | Click Try again.
You see | What it means | What to do
"The automation failed. The reason is in its history." | The last run ended with an error. | Open the automation history and read the reason. Then ask the builder in the chat to fix it, quoting the reason.
"The test failed." | A test run did not finish. | Read the history, fix, and test again before you turn it on.
"Paused: it ran more than 30 times in one minute. An automation that changes the record that started it starts itself again. Change what it does, then turn it back on." | The automation kept starting itself, so it was stopped to protect your app. | Ask the builder to change it so it does not edit the record that starts it, then turn it back on.
"We could not update the automation." | Turning it on or off, or a change, was not saved. | Try again.
"We could not prepare ideas right now. Try again in a moment." | Ideas for this app did not load. | Try again in a moment, or describe the automation in your own words.
Fix an automation that started itself: "The automation "Mark new bookings as handled" paused because it ran more than 30 times in one minute. It runs when a booking is updated and then updates the same booking. Change it so it runs only when a booking is created, and does not trigger itself."
You see | What it means | What to do
"You chose what to be told about, but not where. Turn on email or WhatsApp." | You picked events, but no channel is on. | Turn on Email or WhatsApp under Where to send it.
"Choose above what to be told about. Until then nothing is sent." | A channel is on, but no event is chosen. | Tick A new record or A new user.
"The number is verified, but WhatsApp notifications of this app go to the number of the app's owner." | You are a collaborator, not the owner. | Nothing to fix. Ask the owner, or use email.
"We could not send the code. Check the number and try again." | The WhatsApp code was not sent. | Type the full number with the country code and try again.
"The code is wrong or has expired." | The code you typed does not match. | Click Send again and type the new code.
"WhatsApp notifications are not available right now." | The WhatsApp side is down for now. | Use email meanwhile.
"The summary is sent on WhatsApp. Turn on WhatsApp above first." | A daily summary needs WhatsApp. | Turn on WhatsApp in the section above it.
"The last one was not sent" or "We could not send the summary." | The last daily summary did not go out. | Click Send now to test it. If it fails again, check your WhatsApp number is verified.
Every form in your app saves what people type as a record in a table of your app's database: a booking form saves a row in Bookings, a contact form a row in Leads. Open the Database screen in the Studio to see them, export them or edit them. See The database.
To hear about each new answer, open Notifications and tick A new record ("Someone filled in a form, or a new row was added to one of your tables."). For a daily count, click Add a summary and write the question, for example "How many new leads came in today?".
1. Look at it in the phone size: In the preview, switch between Desktop, Tablet and Mobile. Then open the live address on your own phone.
2. Tell the AI what you see: Name the page and the problem, as in the example below.
3. Let the Testing Agent check: The Testing Agent goes through the app like a visitor and reports what broke. See Testing agent.
4. Check Page loading acceleration: In General Settings, Page loading acceleration set to automatic prepares eligible pages before visitors arrive. "Forms, personal data and A/B tests continue to run live."
5. Publish again: Fixes reach visitors only after you publish.
Describe a phone problem: "On a phone, the booking page is cut on the right and the Book button is hidden under the menu. Fix the mobile layout of this page only, without changing the desktop design."
Render Mode in General Settings has two choices: Application (SPA) loads everything at once, so moving between pages is fast; Website (per page) loads only the page that opened, so the first page shows sooner. A site that people mostly visit once, such as a landing page, usually fits Website (per page).
When to open a ticket: You deleted an app by mistake, or a setting will not save after a reload and a second try. Open a ticket with the app name and the exact message.
Q: Is unpublishing the same as deleting?
A: No. Not published takes the app off its address; the app, its data and its versions stay in your account, and you can publish again any time.
Q: Does Duplicate copy my customers' data?
A: Only if Include app data is ticked. With Chat History also copies the build chat.
Q: Can a deleted app come back by itself?
A: No. Open a ticket; the Saved Versions are kept for 6 months after the delete.
Q: Who gets the notifications of a shared app?
A: WhatsApp notifications go to the app owner's number. Email notifications go to the address you set.
Related: The home screen and My Apps, Studio settings, section by section, Automations: tasks your app does by itself, The database: tables and records, Saved versions and restore