Resyncs the specified pipeline_id by running the historical load again for all of its active objects.
Use the drop_and_load parameter to specify whether Hevo drops and recreates the Destination tables before it loads the historical data again. The request body is optional, and leaving it out is the same as setting drop_and_load to false. With false, Hevo keeps your Destination tables, applies any schema changes to them and loads the data into them again.
When you resync a Pipeline, Hevo performs the following actions:
- Deletes the schedules of the Pipeline and cancels the jobs that are running.
- Releases the resources that Hevo created in your Source, such as the replication slot on a PostgreSQL Source.
- Reads the Source schema and the Destination schema again, and resets the object mappings.
- Restores the schedule of the Pipeline. If
schedule.sync_typeisON_DEMAND, the sync starts immediately.
If the resync fails, the Pipeline moves to the Failed state. Read Resync Pipeline for more information about the actions performed on your Pipeline when you resync it.
The response returns the Pipeline in the Restarting state, and the Pipeline reaches the Initialized state once the action completes. To re-ingest particular objects without resyncing the whole Pipeline, use the Trigger Resync for a Set of Objects endpoint instead.
Refer to Resyncing a Pipeline for more information about when and how to resync a Pipeline.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
The Pipeline could not be resynced. This occurs when:
- The Pipeline is not in the
InitializedorFailedstate. A Pipeline that failed while it was being deleted cannot be resynced. - The request body is not valid JSON, or the
drop_and_loadvalue is not a boolean.
You do not have the permission to run this action on a Pipeline. Ask your team administrator for a role that allows it.
The Pipeline could not be found. This occurs when:
- No Pipeline exists with the specified
pipeline_id, or you do not have access to it. - The Pipeline is deleted, or its deletion is in progress.
- The Pipeline is in a different region from the base URL that you call.
The Pipeline could not be resynced. This occurs when the Pipeline is changing state, for example when it is in the Enabling or Disabling state. Retry the request once the Pipeline reaches a stable state, such as Initialized.
Another operation on the Pipeline is already running. Retry the request a few seconds later.