Before changing anything, write down the page, action, result, and expected result. Check access and assigned resources before rebuilding the app.
-
Identify the page
Note where the problem happened and which person or role was affected.
-
Repeat once
Record the exact action, result, and expected result.
-
Check access and resources
Confirm member access, Share settings, assigned Knowledge, Connectors, and Configs as relevant.
-
Report the problem
If it still fails, use the bug icon in the app header or email
[email protected].
An app change is not visible
Changes requested through chat appear without publishing. If you edited code manually, confirm the save succeeded and reload the app. Publish is optional after a manual page edit and only updates the separately published version; it is not required to use or share the app.
A member cannot open an app
Members only see apps and coworkers on their access lists. Open Settings, then Members, and check the member’s row: it shows how many apps and coworkers they can reach. Use Manage app access to add the missing app.
If they are reaching the app through a Share link instead, check the link’s own settings: it may require workspace membership, or a passcode. Note that there is no email or domain allowlist in Appaca, so if someone cannot get in, the cause is their invitation, their role, their access lists, or the Share link settings.
A connector cannot find a resource
Confirm the account you authorized actually has access to the Google, Slack, or Airtable resource, since Appaca can only see what that identity can see. Then confirm the connector is assigned to the app or coworker doing the work; authorizing it at the workspace level is not enough on its own. Reauthorize only when the account or its permissions changed, because reauthorizing does not fix an assignment problem.
Knowledge answers are missing or outdated
Check the source’s status on the Knowledge page. Only sources marked Ready are available to apps and coworkers, and a source stuck on Processing or showing Failed will silently contribute nothing.
If the source is Ready, confirm it is assigned to the specific app or coworker you are asking. If answers are outdated, look for an older copy of the same document still attached, since Appaca will retrieve from both and cannot tell which one you consider current. Delete the stale one.
A source failed to process
Failed sources cannot be retried. Delete the source and upload it again. If it fails a second time, the file is likely one of these cases: larger than 10 MB, a PDF longer than 500 pages, or a scanned PDF that contains images of text rather than text. For a scanned document, run it through OCR first, or paste the content into a plain text file.
An automation did not run
Check that the scheduler or Pulse is still enabled, since an invalid schedule can disable a Pulse automatically. Then confirm the time you expected: app schedulers run in UTC with no timezone option, while Pulses run in the timezone of the browser that created them.
For a Pulse, open Run history on the Pulse and use View chat on the run to see what the coworker actually did. App schedulers keep no run history, so if you need to see their outcomes, have the function record its own result somewhere you can read.
An external agent can read but cannot change an app
Check the scopes on the connection. apps:read does not imply apps:build or apps:write, and each is granted separately. Add the scope only if that client genuinely should make changes, and prefer the narrowest scope that works.
A coworker asks a question during a scheduled run
This makes the run fail, because a scheduled run has no one to answer. Rewrite the Pulse prompt so it stands alone: name the timeframe, the source, and the output format, and tell the coworker what to do when data is missing rather than leaving it to ask.
When you still need help
Gather the workspace, the app or coworker name, roughly when it happened, the role of the affected person, the steps to reproduce, and any error text. Remove secrets and customer records from screenshots before sharing.
For a problem inside an app, select the bug icon, enter a message, and optionally attach one JPEG or PNG image. For anything else, email [email protected].