Troubleshoot native operations

For agents: Read the complete native guide and current context.get capabilities. Use only implemented operations and preserve exact Account, app and environment authority.

An accepted request means work was recorded, not that the app is live. Poll operations.get and distinguish waiting, failed, cancelled, succeeded and unknown cleanup. Reuse an idempotency key only for identical intent.

For revision or epoch conflicts, retrieve current app state before retrying. For a lost provider reply, let the operation reconcile the same reserved resource instead of allocating another one. Do not expose a candidate whose readiness or authority is unconfirmed.

For build errors, inspect untrusted diagnostics and patch the original source. For app errors, test the exact preview, inspect owned-generation logs and repair the flow. Browser evidence and data rows require full publishing access. Missing credentials use protected entry; generated app secrets should not require a user action.

A stopped app can retain data and storage charges. A successful code switch does not restore data, prove every app workflow, or erase an earlier external side effect. Report these distinctions explicitly.