# Looping Unit Procedures in Recipe Editor Sepasoft Batch

**URL:** <https://forum.inductiveautomation.com/t/looping-unit-procedures-in-recipe-editor-sepasoft-batch/68508>\
**Category:** 3rd Party Modules\
**Tags:** sepasoft\
**Created:** [January 11, 2023, 7:56pm UTC](https://forum.inductiveautomation.com/t/looping-unit-procedures-in-recipe-editor-sepasoft-batch/68508 "2023-01-11T19:56:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Kienzle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nick_kienzle/32/42548_2.png) [@Nick\_Kienzle](https://forum.inductiveautomation.com/u/Nick_Kienzle)\
**Post date:** [January 11, 2023, 7:56pm UTC](https://forum.inductiveautomation.com/t/looping-unit-procedures-in-recipe-editor-sepasoft-batch/68508/1 "2023-01-11T19:56:01Z")

</div>

![sepasoftError](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/f/afc4e21e2b0aab6eab451ff18f6d56e6cee30491.png)

It looks like it's not possible to loopback unit procedures. Per Sepasoft documentation: "The workflow validation does not allow Unit Procedures and Operations to exist inside of loopbacks".

Will there be any future support on this? This is possible and allowed to do in FTBatch. I'm considering migrating from FTBatch to Sepasoft Batch and I'd like to keep the same functionality I have currently especially to reduce any additional validation efforts (in a regulated environment).