-
Bug
-
Resolution: Won't Do
-
Critical
-
None
-
None
-
False
-
-
False
-
-
-
Critical
Description of the problem:
Second or later workflow execution contains output from the first one instead of the actual one.
How reproducible:
Always
Steps to reproduce:
1. execute a workflow (observed on wait-or-error)
2. as expected: during the workflow execution and after its completion, the /v2/workflows/instances/:id response contains both progress or final data as expected.
3. re-execute the same workflow
4. issue: during the execution (not sure about final state), the /instances/:id response contains final data of the previous execution no matter the workflow has already produced intermediate data (as by this step: https://github.com/parodos-dev/backstage-orchestrator-workflows/blob/main/workflows/wait-or-error.sw.yaml#L31 .
The actual data returned incorrectly conform this step instead: https://github.com/parodos-dev/backstage-orchestrator-workflows/blob/main/workflows/wait-or-error.sw.yaml#L50
When tracking it down, the
https://github.com/janus-idp/backstage-plugins/blob/main/plugins/orchestrator-backend/src/service/OrchestratorService.ts#L102
already returns this "stale" data for two different instanceIds.
Actual results:
Content of the workflowdata contains data of previous execution
Expected results:
Content of the workflowdata should be exclusive for a particular execution.