​@TntKirtaS if you have a BPA WF that is firing when releasing blocked orders, then you need to rework the BPA WF. Or at least undeploy it until you have figured out what the error is.

You could start a Watch on that BPA WF and debug it so that you could fix the issue.

Unfortunately there isn’t much the community could do at this point, without seeing the BPA WF and what it’s trying to do.

​@TntKirtaS By default, 20 workflows can be triggered in a single database transaction. The “infinite recursion" error means that the workflow(s) is getting triggered too many times in the same transaction.

https://docs.ifs.com/techdocs/24r1/040_tailoring/500_business_process_automation/025_considerations/

I don’t see this verbiage in the 24r2 and 25r1 documentation, so there may be a different solution there, but we are still on 24r1, so I can’t say for sure.

Depending on what the workflow does, you could try changing the timing to asynchronous, but that may not fit your use case. If not, just as ​@Marcel.Ausan suggests, you may need to redesign the workflow, or at least the trigger.