Skip to main content

Import status and recovery

For a stalled Microsoft import, inspect the mailbox state and safe error code first. Worker health, queue acceptance, import completion, and search readiness are separate states. See Graph setup for provider prerequisites.

From the motherrepo root, an operator can inspect the instance with:

bash devstack.sh status

Use the daily runtime guide for logs and scoped recovery. The current development path uses Docker. Do not add an independent manual backend or onboarding worker beside it.

SymptomCheck
No processing startsWorker availability, Kafka connection, durable run
Storage failurePostgreSQL/S3 access and recorded object key
Waiting for a keyCorrect owner key setup and unlock
Indexing incompleteSearch service and this import's indexing stage
Browser state staleCurrent authenticated server state and connection

Prefer continuation from a saved checkpoint. A full reset deletes data and is not general repair. Reset and cleanup are unsupported in partialRemote, including simulation. Do not switch to local mode to bypass that restriction.