Cancel Sync Job
Request cancellation of a running sync job.
State lifecycle: PENDING / RUNNING → CANCELLING → CANCELLED
- The API immediately marks the job as CANCELLING in the database.
- A cancellation signal is sent to the Temporal workflow.
- The worker receives the signal, gracefully stops the sync pipeline (cancels worker pool, source stream), and marks the job as CANCELLED.
Already-processed entities are retained in the vector database. If the worker is unresponsive, a background cleanup job will force the transition to CANCELLED after 3 minutes.
Note: Only jobs in PENDING or RUNNING state can be cancelled.
Attempting to cancel a COMPLETED, FAILED, or CANCELLED job returns 400.
Authentication
Path parameters
Unique identifier of the source connection (UUID)
Unique identifier of the sync job to cancel (UUID)
Response
Current status: PENDING, RUNNING, COMPLETED, FAILED, CANCELLED, or CANCELLING
When the job started execution (ISO 8601)
When the job finished (ISO 8601). Null if still running.
Error category for credential errors (e.g. oauth_credentials_expired)