Re-ingests all the data for the objects that you name in the specified pipeline_id. The schedule, the state of the Pipeline, and every object that you do not name are left unchanged.
List the fully qualified names of the objects that you want to resync in object_names, up to 50 in a single request. A fully qualified name is the database, the schema and the table of the object joined by dots, leaving out any level that your Source does not have. For example, public.orders or shop.public.orders. Retrieve the names from the List All Pipeline Objects endpoint. To resync every active object instead, use the Resync a Pipeline endpoint.
Use the drop_and_load parameter to specify whether Hevo drops and recreates the Destination table of each object before it loads the data again.
Refer to Resyncing Objects for more information about the actions performed on your objects when you resync them.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
The resync could not be initiated. This occurs when:
- The Pipeline is in the
DisablingorDisabledstate, or it failed during setup, enable or disable. A Pipeline in any other state, including one that is initializing or being enabled, is not rejected. - The
object_nameslist is missing or empty, names more than 50 objects, or contains a blank name. - A named object is not selected for replication. Select it with the Manage Objects in a Pipeline (PATCH) endpoint, which loads its data for you.
- A named object has a parent object. Hevo resyncs such an object along with its parent, so name the parent object instead. This rejection applies to an object for which the List All Pipeline Objects endpoint does not return the
selectablefield. - A named object does not allow a resync in its current state. Hevo checks the object’s
resync_allowedvalue. - A named object is in a status that does not allow a resync. Only an object in the
ACTIVE,INCONSISTENTorRESETTINGstatus can be resynced.
You do not have the permission to modify a Pipeline. Ask your team administrator for a role that allows it.
The Pipeline or an object 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.
- A name in
object_namesis not an object of the Pipeline.
The resync could not be initiated. This occurs when a resync is already running for one or more of these objects. Wait for it to finish. Use the List All Jobs for a Pipeline endpoint to see the job that is running.