And let me explain my use case.
The payload for the workflow is below
Payload is sent to main flow execution
When the subflow is invoked the complete payload is again sent to subflow, as the nested subflows are possible
This is the main reason I guess for the history size increase.
Thinking of the below solution. Can you please validate the following solution?
Maintain the complete payload in the main workflow.
Implement a query method in the main flow to return by taking a subflow name as an argument and return subflow payload and cache it as one of the flow instance variable
When a child flow requires subflow payload, use the query method of the main workflow to get the same.
We have a case where the subflow1 can be executed in parallel(using child flows) where the work is distributed say 10 child flows each handles 10 iterations). I am using the promise to complete the child flow as below.
JiffyWorkflow workflow = WorkFlowUtils.buildChildWorkFlowObject();
One question I have is “will this work in case of child flow crashes also”?