Troubleshooting
Common Autonomous Work problems.
- A run says "waiting for permission" and never progresses — is it stuck?
- No — this is the expected, honest behavior when the run needs a confirmation an unattended process can’t supply (e.g. installing a tool, running an unlisted command). See Permissions above. Resolve it by running the equivalent request in a normal chat session where you can confirm it directly.
- Where do I see the result of a run?
- In your Ticket Wallet history (what was fixed, files changed, evidence and charge), and as a comment on your GitHub pull request or GitLab merge request when one is linked.
- Was I charged for a run that didn’t finish?
- No — see Completion & Charging. Only a genuinely, server-side-confirmed complete run deducts from your balance.
How it works
What you see
- An unattended run for a ticket: investigation, plan, implementation, checks, completion and charge.
- Eligibility, connection status, your Ticket Wallet balance, ticket details, evidence and the final result.
- Before/after evidence and a summary of what was fixed, in your Ticket Wallet history.
What PawOS does
- PawOS investigates the ticket and repository, works in an isolated copy, applies and checks the fix, and records evidence.
- Ticket Wallet credits are separate from Paw Compute and are charged only when a ticket is successfully completed.
- Each ticket is charged at most once.
Permissions
- Autonomous Work never installs software, changes system settings or skips your organization’s approval rules.
- Each connected service offers specific actions — see Connectors for what each one supports.
- A blocked, failed or unverified run is never reported as completed.
Records
- Completion is backed by the repository state, check results, changed files and the charge record.
Good to know
- You need an eligible plan, a connected account, a repository and Ticket Wallet credits to start a run.