Most app problems fall into three groups: the app will not build, a change is not showing up, or an action does nothing. Check the status badge in the app header first.
Reading the status badge
| Badge | What it means |
|---|---|
| Crafting… | The app is being created for the first time |
| Deploying… | A build is running; the new version is not live yet |
| Fixing… | A build failed and Appaca is attempting to repair it itself |
| Error | The build failed and automatic repair gave up |
| Active | The app is built and running |
While an app is deploying or fixing, the chat input is disabled. That is expected, not a fault: wait for the build rather than reloading.
When a build fails
Appaca tries to fix build failures automatically. An app that briefly shows Fixing… and returns to Active needs no action.
If recovery fails, the app shows Error.
At that point you have two useful moves:
Revert to the last working version. The error state offers Or, revert to last version, which restores the most recent snapshot. This is usually the right first step: get back to something that works, then approach the change differently.
Ask for the change in smaller pieces. A build that fails repeatedly is often one large request touching several pages and functions at once. Ask for one page, verify it, then the next. Smaller changes fail less and are far easier to diagnose when they do.
A change is not showing up
Changes made through chat appear in the app without publishing.
If you edited code manually:
- A function edit takes effect when saved.
- A page edit appears in the current app when saved.
- Publish is optional after a manual page edit and updates only the separately published version.
Publishing is not required to use or share an app.
A function returns nothing
This can look like a blank result or a form that submits without confirmation.
-
Check Data
Open Data and confirm whether the expected records exist.
-
Check access
Confirm the app has the required Data and Connectors.
-
Check Configs
Open Settings, then Configs, and confirm required values are present.
-
Show the result
Ask Appaca to display a clear status and result count in the app.
A chat message failed
A message showing Failed to generate response can simply be retried. If it fails repeatedly on the same request, the request is usually too large: break it into separate, smaller asks.
Someone cannot open the app
This is an access problem rather than an app problem. For a workspace member, check their app access list on the Members page. For someone using a Share link, check the link’s membership requirement and passcode. Neither has anything to do with the app’s build state.
Reporting a problem
The bug icon in the app header opens a report where you can describe what happened and attach a screenshot. Include the page, what you did, what you saw, and what you expected, since a report saying the app is broken cannot be acted on.
For anything outside a specific app, email [email protected].