Skip to content

Restore callback troubleshooting lost in a merge #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jacobprall merged 1 commit into from
Oct 31, 2026
Merged

Restore callback troubleshooting lost in a merge #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/0_QUICKSTART.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -305,8 +305,10 @@ events with `"ok": false`; a failed refresh leaves the previous snapshot availab
Authentication failures usually mean the model key is missing or invalid.
- **Infrastructure retries exhausted:** inspect failed `investigate` task
runs. Restore timeouts and Sandbox verification are common causes.
- **Callback never arrives:** inspect `deliver_failed` and the `deliver`
subtask's attempts. The receiver must return 2xx within 10 seconds.
- **Callback never arrives:** a `deliver_skipped` event means the callback's
origin isn't in the workflow's `CALLBACK_ALLOWED_ORIGINS`. Otherwise,
inspect `deliver_failed` and the `deliver` subtask's attempts. The receiver
must return 2xx within 10 seconds and must not redirect.
- **First request is slow:** the free API instance spun down after 15 idle
minutes. Switch it to Starter in `render.yaml` to keep it warm.

Expand Down
Loading