# Testing, Starting, and Stopping Recipes


In Workato, you can work with recipes in various ways:

  • test a recipe to run a single trigger event through the recipe logic
  • start a recipe to have it pick up trigger events
  • stop a recipe to have it stop processing new trigger events
  • use skip step to build and test your recipes incrementally

# Testing Recipes

Workato's integrated recipe testing environment allows you to test your recipe before starting it. Testing ensures your automation's behavior and data processing are correct - you don't want to do a lot of clean-up later!

During recipe development, we recommend building and testing in small chunks. To enter test mode, click Test jobs or the Test button in the top right corner of the Recipe editor:

Test mode toggle and button in the Recipe editor Test mode toggle and button in the Recipe editor

Refer to the Testing recipes guide for a detailed look at Workato's test environment.


# Starting Recipes

Starting a recipe will cause it to pick up trigger events and process them through the recipe. When a recipe is started, it becomes active.

# Starting A Recipe For The First Time

When a recipe is first started, it will fetch trigger events from the When first started, this recipe should pick up events from configuration. Subsequently, it will continuously process these events. If you had defined the Since/From date during testing previously, this date cannot be changed again for this recipe - learn more here.

If you had tested your recipe in test mode before starting, the recipe will not reprocess any trigger events previously picked up during testing. This prevents duplication of data in your apps. You should only start your recipe when you've fully tested it - check out the section on testing recipes if not.

If you have any successful jobs, the start button should be displayed by default. Otherwise, it can be found in the dropdown list.

Default start button Start button showing up on default for a recipe with at least 1 successful job

# Starting A Recipe For The Second Time

For most Workato recipes, when a recipe is started after it has been stopped previously, it will continue where it was 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 recipe. You can read more about real-time triggers and webhooks here.


# Stopping Recipes

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 Workato 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 Workato 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 recipe. You can read more about real-time triggers and webhooks here.

# Recipes Stopped By Workato

Some recipes are stopped by Workato. In such cases, you will receive an email from us about this stopped recipe. There are 2 reasons for this:

  1. Recipes are automatically stopped when the monthly transaction limit is hit. Contact our customer success team to add more transactions.

  2. The recipe has experienced 60 consecutive errors when trying to fetch trigger events. This can be due to various causes, for example, 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.

consecerror Error message shown in the recipe when there has been 60 consecutive trigger errors

# Notification Emails

When a recipe is stopped by Workato, an email is sent to the login email associated with the Workato account. This email can be changed, and additional recipients can also be added to be notified via the Notifications email setup in your account settings.

notemail Configure the emails to notify in account settings