@ntabs
Stet-by-step debugger mode doesn’t allow you to execute and analyse each step separately in live mode. All backend WFs/steps shoot as soon as you trigger the main WF and what you see while jumping between steps in debugger is a result of what already happened:
This makes debugging WFs/actions that are deleting multiple things that are connected with each other complicated (especially, if you have some satellite or related Data Types).
What helped me to solve a problem similar to yours:
- I’ve created custom states to store things-to-delete and wrapped them in a custom event that was placed first in my main WF. While deleting things in subsequent WFs/actions (also wrapped in custom events) I was referencing Things from custom states, not something from a group/rg/current page.
- Checking the flow in Server Logs.
P.S. I my case I wasn’t dealing with API calls, so my suggestions above may not be helpful for your.