Account

Troubleshooting

Troubleshoot datawebot. sign-in, Jobs that are still running, low balance, partial results, expired results and rejected keys.

Job still running

A running Job returns poll_after_seconds. Poll no faster than that and set an upper bound on how long you wait.

Resending a submission with the same Idempotency-Key returns the same Job; a new key creates a separate Job with its own credit hold. Contact support with the Job ID if a Job stays running.

Low balance

insufficient_credits (HTTP 402) means your balance can't cover the Job's credit hold. Ask for fewer pages to lower the hold, or buy more credits on the dashboard under Billing. Search and seller offers do not use credits.

Partial or missing data

A timeout, source error or blocked page makes a Job failed or partial, not empty. Failed and empty Jobs are free. Fields can be absent and the accessible catalogue may differ from the full merchant database.

Keep currency, scope and retrieval time when comparing output with a page viewed later. Personalized prices or filters can show different values.

Expired results or rejected key

Results are kept for seven days after a Job finishes; after that, results_expired (HTTP 410) is returned. Run a new Job for a fresh observation. HTTP 401 means the key is missing, expired or revoked.

Never send credentials, login links or payment details to support. Use the Job ID, the X-Request-Id header and the error code.

Need help? Contact support.