Skip to main content

Reset job state

POST 
/platform/jobs/:jobId/reset-state

Reset incremental state so the next job execution starts from the beginning. This cannot be undone: the previous bookmark is cleared. Reset is immediate but does not itself trigger execution; consider the volume and downstream deduplication before re-syncing.

Connector behavior​

  • JDBC clears incremental_column_value; the next incremental execution extracts all available records. Full-load jobs already extract everything.
  • Singer clears state_file bookmarks.
  • S3 clears ConnectorState so previously processed files can be processed again.

Example request​

POST /platform/jobs/1b33ad2f_33d3_4837_9eeb_83c82c8b909d_0/reset-state

Source success fields include status: true, detail and a message about the next extraction. Source 404/500 examples are not enumerated in the imported response map.

For a JDBC-only partial rewind, source guidance uses Patch job input with connector: jdbc and a past incremental_column_value, for example 2024-01-01T00:00:00Z. This is not a partial-reset feature for Singer or S3. Wait for the next schedule or explicitly execute the parent pipeline after resetting.

Request​

Responses​

Job state reset