# Skip step
Skip step allows you to isolate (e.g. ignore) segments of your recipe at run-time. A skipped step or skipped block will not be processed during testing or at the start of the recipe. The datapills from those actions will not be available for use by subsequent actions.
A skipped step will not be processed at run-time and its datapills will not be available
# When to use skip step
Skip step allows you to ignore steps when running a recipe. This is very useful when you’re trying to build a recipe, and only want to test a part of it.
Some scenarios where this can useful:
|Building a recipe incrementally||If you’d like to build out a high-level logic of the entire recipe but configure some steps later, then you can test only the portion of the recipe you’ve already configured by skipping all the remaining unconfigured steps.|
|Iterating between different logic flows||If you’d like to try different logical methods in a recipe, then you can take turns skipping steps related to each method and iteratively test which one works better.|
|Faulty steps during recipe building||If you’re encountering design-time errors due to broken connections, incorrect formulae, or missing configurations, then you can simply skip those steps, and still test the remaining recipe.|
# How to use skip step
Skip a step by clicking on the skip step icon. You can see the icon when you hover on the action.
Skip step icon
A skipped step will be hashed out. This step and its datapills will not be available at run-time.
Select the unskip step icon to revert.
Unskip step icon
When a step is selected, use the keyboard shortcut (
/) to toggle between skipping and unskipping it.
# Skip action block
Rather than skipping individual actions, skip a logical group of actions with skip action block.
skip for the following action blocks:
- Conditional blocks
- Repeat blocks
- Error monitor blocks
This works the same way control flows are intended. A conditional statement is logically tied to the conditional actions. Thus, if the conditional block is skipped, the nested steps will be skipped as well.
A skipped repeat block. All nested actions will not be processed at runtime
# How to use skip action block
Skip an action block by selecting skip block on a parent step (e.g. a repeat step). This process is identical to skipping a single step.
When the parent node of an action block is skipped, all nested steps are automatically skipped.
To undo skip on an action block, you must select unskip from the parent node. It is not possible to unskip a single action step that is nested within a skipped action block. You can either skip/unskip an entire block or keep the block active and directly skip/unskip its child steps.
Skipped block datapills
All steps within a skipped block will not be available at run-time.
# What happens to datapills in skipped steps
When you skip a step, all dependent steps break when you try to run the recipe. Subsequent actions that rely on datapills from a skipped step will return an error.
For example, this recipe returns and error during testing. The step is referencing datapills from an earlier step which has been skipped.
Datapills in a skipped step/block will not be available
# Can triggers be skipped?
No. Since we need an event to kickstart the recipe, Workato does not support skipping triggers. Only recipe actions can be skipped. See here for an overview of recipe actions.