Outway documentation

Troubleshooting

Resolve Outway authentication, collection, budget and asynchronous job errors.

Request failed

StatusWhat to check
401Credential validity and sign-in session
403Scope, project access and administrator requirements
409Conflicting idempotency or resource state
429Rate limits; respect retry guidance
503Service or source integration availability

Keep the response details and request identifier when available, but remove tokens before sharing diagnostics.

Job did not finish successfully

Queued, running and waiting-retry states are not successful captures. Handle failed, cancelled, blocked-budget and submission-unknown outcomes explicitly. Inspect partial results before retrying. Use delays between polls and bounded client timeouts.

Target is blocked

Check that the URL is public and uses a supported scheme and port. A challenge or blocked source can prevent collection. Browser rendering is not a guarantee that a source will permit access.

Usage looks different

Compare the requested-unit subscription balance with key caps and project budgets. Completed-result diagnostic units measure something different. See Plans and usage.

Need the exact contract?

Use the published OpenAPI schema, including endpoint permissions and response definitions. Do not assume a third-party scraper’s request body works with Outway.

Need help?

For account or connector support, email [email protected]. Include the request ID and error details when available, and remove access tokens and other secrets before sharing diagnostics.