Troubleshoot a request

No result

Check that the input identifies the right entity and the requested fact is available. A company name alone can be ambiguous. Review sources before changing the question. An empty result is not proof that the real-world fact does not exist.

Failed job

Read errorCode, the job ID and any displayed explanation. Distinguish invalid input from a temporary service error. Correct a schema error before submitting a new task. For an uncertain paid outcome, inspect the original batch first; keep its retry identity.

Job remains running

Reload Activity or call enrichment.get for the existing batch. Closing the browser does not stop the backend. If the state does not progress, contact support with the ID and time instead of dispatching another copy.

Access denied

Confirm the environment, workspace, membership and key or OAuth scope. A local development login does not authorize production. A key tied to one workspace does not follow the workspace switcher. Use authentication to verify the connection.

Unexpected costs

Compare the requested workflow to a direct-tool estimate. Research can involve multiple actions; an empty answer can still follow paid research. Wait for billingStatus: "settled" before treating credits as final. Report remaining reservations with the original IDs.

Rate limiting

Back off on 429. Reduce request frequency and polling, and respect any retry guidance. Do not replay the same paid task with new keys to work around a limit. See bulk requests.