Troubleshooting

Find up-to-date explanations of different types of errors and pointers on how to resolve them.

Academic verification is required for computationally or network-heavy tasks. This is to ensure that the resources are not being misused. You may verify yourself after registering on the platform — see Authentication for details on CILogon verification.

Dataset

A dataset belongs to the creator, and groups that the creator chooses to share its ownership. If you are unable to access a dataset, you fit neither of these categories. You may request access to the dataset from the creator.

429, Too Many Requests

You have exceeded the rate limit (100 requests/second by default). Respect the Retry-After header and implement exponential backoff. See Rate Limiting.

Job Failures

If a submitted job fails:

Check the job status: GET /v1/jobs/{job_id} — the error_message field describes the failure
Common causes: query timeout, result too large (>1 GB), ClickHouse resource limits
Rerun the job: POST /v1/jobs/{job_id}/rerun

See Jobs System for details.

SyQL Errors

Parse errors: Check SyQL syntax in the error message. Use POST /v1/syql/plan to validate without executing.
Resolution errors: A referenced table or column does not exist. Check the Data Structuring guide for valid column names.
Timeout: Large queries may exceed the 60s HTTP timeout. Use POST /v1/syql/exec to submit as an async job instead.

Federation Issues

See Federation Troubleshooting for:

Node discovery failures (mDNS, multiaddrs)
Schema version mismatches
Cluster health states
Docker Compose federation profile issues

Synapse DB