# Build recipes in small steps
When building a recipe, it is recommended to build each group individually. As each group is building separately, managing recipe logic is simpler and it will be easier to catch and debug recipe errors
Skip step causes the recipe to ignore that step or block at runtime. The datapills from the skipped 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 want 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 have already configured by skipping all the remaining unconfigured steps.|
|Iterating between different logic flows||If you would 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 are 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.|