BPMN Backward Flow

We have a requirement where for a specific scenario, the process should move from activity D to activity C. I have added a boundary signal event at activity D which on triggerred, will take the flow backwards and keep the flow waiting at activity C.

Would like to know whether this is a proper approach to achieve the requirement. Any suggesstion to improve this would be helpful.


instead you can try using HTTP API to move the task back to C only for a specific scenario which makes process more align to the business.

Thanks @hashdhi for the response, but could you please explain in detail.

The process is waiting in activity D for user action to be completed, so how does http api comes into picture here ?