Reset recipe trigger
Reset recipe trigger cursor by recipe ID for a customer. Use this endpoint to re-sync data from the source application. The recipe should be designed to handle duplicate records because a re-sync processes every record again. Using this endpoint outside data integration scenarios may result in unintended behaviors, including data loss or corruption. Resetting a recipe trigger retains job history and records an event in the recipe’s Activity audit log.
If the trigger is reset on an active recipe, running, deferred, and pending jobs run and complete before proceeding to the new jobs created by the reset trigger.
This endpoint is only compatible with polling and scheduled triggers. Resetting other triggers may have no effect, or cause unintended behaviors. These triggers include:
- New CSV file in folder triggers
- Function triggers
- API triggers
- RecipeOps triggers
- Workbot triggers
- Kafka triggers
Path parameters
Embedded customer ID (external ID). The External ID must be URL encoded and prefixed with an E
. For example, EA2300
.
Headers
Bearer authentication of the form Bearer <token>, where token is your auth token.