The Activity view
The Activity tab on your Actions page shows every run. Click any entry to open the run detail.
Reading a run
The run detail shows a structured breakdown across four layers. For successful runs, each layer simply confirms what happened — user request, wizard stage, action called, policy satisfied. The same view shows where a failure originated when a run breaks.
Proposed fix:
What gets logged
Run detail: conversation on the left, failure breakdown on the right with a specific proposed fix
Retention
Execution logs are retained for 12 months. Identifiers likeorganizationId or workspaceId are never persisted — they’re injected into the AI’s system prompt for the request, then discarded. Only userId is stored. See Policies → Data and privacy for the full breakdown.
Common error types
Validation error (422)
A required field was missing. Fix: add the field toRequire: in the action’s Booster.
Network error (status 0)
The fetch threw before a response was received. This usually means the snippet ran before the user was authenticated, or your API doesn’t accept requests from the user’s browser origin. Check CORS headers and that your endpoint is reachable from the browser.Action not found
The AI called an action ID that doesn’t exist in the loaded registry. Usually means an action was removed fromactions.json without redeploying.
Auth failure (401/403)
YourfetchFn may be reading a stale token. Read it fresh on every request rather than closing over an initial value.