Troubleshooting
Start with a reproducible task. Record the app, approximate time, steps, visible result, and expected behavior. Keep private records and credentials out of support messages.
A build or edit did not finish
Section titled “A build or edit did not finish”Check the reported status and any usage or validation error in Studio. Avoid repeatedly submitting the same request while a build is still active. Once its state is clear, make the next request specific to the problem.
Information is missing
Section titled “Information is missing”Confirm the app, account, and dataset, and whether you are looking at the preview or the live app. Refresh and inspect a known record. Sample information in a preview is not proof of persistence. Review the app’s data connection and permissions before re-importing, which may create duplicates.
A person cannot sign in or see a record
Section titled “A person cannot sign in or see a record”Check the selected sign-in method, published hostname, and the person’s role or ownership. Reproduce with a test account. Do not fix a private access error by making all records public.
The published link fails
Section titled “The published link fails”Check the app’s publishing status in Studio, domain verification for a custom domain, and any usage condition shown for that app. A published app does not expire. A website maintenance page does not establish the status of every published app.
A model or agent fails
Section titled “A model or agent fails”Inspect the input, available context, model configuration, and usage for the affected operation. Use a small example, then test the recovery path. A plausible response may still be incorrect; compare it with the source material.
Old API examples return 404
Section titled “Old API examples return 404”The old /v1/apps lifecycle API and /v1/openapi.json are not registered in the current service. Use the current interface guide; Studio is the present app creation and publishing path.