When troubleshooting your recipe, with all the frustration it is easy to forgot what are the right ways to test out the recipe and see if it works. Here are four ways of refreshing your recipe and jobs for different scenarios.
Refresh Schema and Save
Refresh Schema and Save button can be found in the drop down menu of Save at the end of your recipe. Refresh your schema when there are changes in your app such as new fields, new types, or new objects. Refreshing schema will pick up these new changes in your apps and serve it to you on your recipe.
Start and Stop Recipe
Start and stop a recipe allows you to restart the polling cycle. As mentioned on the website, the Community Edition polls for new triggered jobs every 30 minutes. If you'd like to shorten your troubleshooting time, try stopping and starting the recipe again. This will restart your polling cycle and pick up any test triggers you had just created.
Repeating a Job
Repeating a job will use the retrieved input and the updated recipe to reprocess the failed job. Note that however, Repeating a job still uses the same trigger. This is because the job is only activated because of the trigger, hence changing the trigger will not affect the behaviour of the job.
Copying a recipe
Copying a recipe can be necessary at times. When you have an enormous amount of failed jobs that will take many weekends to repeat all of them, your best bet would be copying the exact recipe and rerun it. As ran jobs will not be picked up again by the same recipe, Copying the recipe will pick up all those jobs anew and run them in your newly cloned one.
Adam Goh
Refresh, Copy, or Repeat? Testing your recipe
When troubleshooting your recipe, with all the frustration it is easy to forgot what are the right ways to test out the recipe and see if it works. Here are four ways of refreshing your recipe and jobs for different scenarios.