Skip to main content
FetchSandbox Docs

Troubleshooting

Timeouts, auth errors, tunnels and missing evidence.

Timeout or lost response

If a provider call timed out or you got a lost response, the outcome can be unknown. Before you retry, confirm whether the original effect happened. Keep dependent actions waiting. Don't blindly resend. If the provider supports idempotency, use the same key so a retry can't create a second effect.

429

The request was rate limited. Wait before you retry. If an earlier attempt's outcome is unclear, follow the timeout steps above.

401

Check your account key and the auth header in your private config.

App not reachable

For a local app, make sure your tunnel is active.

Missing evidence

If a check has no evidence, don't call it a pass.

Job still running

Keep polling the same get_job.