Assistance Needed with Child Workflow Caching Issue in BuildShip
I have encountered an issue with workflow execution that I need assistance with.
I have created a parent workflow that incorporates a child workflow, which is used in three different places within the parent workflow. However, I’ve observed that when the child workflow executes for the first time, it caches the data. As a result, when the child workflow runs for the second and subsequent occurrences with different inputs, it still returns the result from the first execution.
Could you please provide guidance on how to resolve this caching issue to ensure the child workflow processes new inputs correctly for each occurrence? Any insights or configuration adjustments to prevent this behavior would be greatly appreciated.
I have created a parent workflow that incorporates a child workflow, which is used in three different places within the parent workflow. However, I’ve observed that when the child workflow executes for the first time, it caches the data. As a result, when the child workflow runs for the second and subsequent occurrences with different inputs, it still returns the result from the first execution.
Could you please provide guidance on how to resolve this caching issue to ensure the child workflow processes new inputs correctly for each occurrence? Any insights or configuration adjustments to prevent this behavior would be greatly appreciated.
