Support · Troubleshooting
Scan stuck or failed
Historical scans are built to survive infrastructure reality: they checkpoint progress, back off on rate limits, and resume rather than restart.
Normal slow versus actually stuck
Watch processed-page counts. Climbing counts mean working — large histories take a while by design. Zero page progress over an hour means stuck: proceed to re-run.
Re-running safely
Scans upsert rather than duplicate; re-running after a stall fills gaps without polluting history. Re-run first, escalate second — most stalls self-heal on the second attempt.
What to send support
Organisation id, scan start timestamp, and the last processed-page count visible. Those three items locate the run in queues and logs immediately.