You can try following
Check After/before-delete event handlers.
Delete behavior on associations (cascade/block) causing issues.
Recursive self-associations leading to infinite deletes.
Entity access/security blocking deletes.
Try deleting a single object to pinpoint, and enable TRACE logging on ConnectionBus_Delete to see the root cause.
As a next step for figuring things out you could add error handling on the exact activity after which the execution of the microflow halts.
On your error handling you could therefore add logs. In the logs you should display all possible error information. Maybe you will figure it out step by step like this.
Hey Brian,
Sometimes the application simply takes a while to process deletes because there are too many objects to delete. However, that doesn't seem to be your case.
In your situation, it would be ideal to set error handling for this activity. To set error handling, you can right-click the action and set error handling:
You can also try to change the logs level on Console -> Advanced -> Set Log Level
Set to Debug or Trace.
If this answer helped you, mark as accepted
Best Regards,
Ricardo Pereira