Stopping a Recipe makes it inactive. It will stop picking up trigger events. Recipes have to be stopped to make changes to the Recipe, or to rename the Recipe.
Most AppConnect Recipes will continue where they have left off when a Recipe is restarted from a stopped state. This depends on the trigger it has.
For most AppConnect triggers, the Recipe will continue to process jobs from when it stopped - for example, if it was stopped on Monday, and started again from Thursday, the Recipe will fetch all trigger events since Monday and process them.
However, this might not be the case for Recipes with real-time triggers powered by webhooks - trigger events that occur during the time that the Recipe was stopped might not be picked up by the Recipes.
Recipes stopped by AppConnect
Some Recipes are stopped by AppConnect. In such cases, you will receive an email from us about this stopped Recipe. There are 2 reasons for this:
Recipes are automatically stopped when the monthly transaction limit is hit.
The Recipe has experienced 60 consecutive errors when trying to fetch trigger events. This can be due to various causes, e.g. password change leading to disconnected connection, API server of the app was down, etc. You have to fix the underlying issue before the Recipe will work.