subflow does not start when not started from starting node

[tbi88]

Describe the bug
I have a workflow which runs itself again as a subflow. The starting node is set to some node in the workflow. When the execution is triggered, nothing is happening. The workflow is not starting at all and aborted after a while. When running the subflow from the workflows starting node, it works fine.

I need to do it like that, since the API is using pagination and therefore need to have a loop to gather all data. Maybe there is a better option for that anyway?

To Reproduce
build a workflow like seen in the screenhots.

Expected behavior
workflow should start from the chosen node.

Screenshots

** Debug logs**

bla:~$ docker logs a7a52f5d1ec3 2>&1 | grep d9b2a5e7-7d94-42be-8862-614e556e0497
2024/03/13 07:00:47 [DEBUG] Ran worker from request with execution ID: d9b2a5e7-7d94-42be-8862-614e556e0497. Worker URL: http://shuffle-workers:33333/api/v1/execute. DEBUGGING:
docker service logs shuffle-workers 2>&1 -f | grep d9b2a5e7-7d94-42be-8862-614e556e0497

bla:~$ docker service logs shuffle-workers 2>&1 | grep d9b2a5e7-7d94-42be-8862-614e556e0497
shuffle-workers.1.gn5ikdzc41ak@soar-worker-01    | 2024/03/13 06:00:42 [INFO][d9b2a5e7-7d94-42be-8862-614e556e0497] Status: EXECUTING, Results: 3, actions: 9
shuffle-workers.1.gn5ikdzc41ak@soar-worker-01    | 2024/03/13 06:00:42 [INFO][d9b2a5e7-7d94-42be-8862-614e556e0497] shuffle.Actions: 9 + Special shuffle.Triggers: 0
shuffle-workers.1.gn5ikdzc41ak@soar-worker-01    | 2024/03/13 06:00:42 [INFO][d9b2a5e7-7d94-42be-8862-614e556e0497] Inside Decide execution with 3 / 9 results (extra: 0). Status: EXECUTING
shuffle-workers.1.gn5ikdzc41ak@soar-worker-01    | 2024/03/13 06:01:12 [DEBUG][d9b2a5e7-7d94-42be-8862-614e556e0497] Rechecking execution and it's status to send to backend IF the status is EXECUTING (EXECUTING - 3/9 finished)
shuffle-workers.1.gn5ikdzc41ak@soar-worker-01    | 2024/03/13 06:01:12 [DEBUG][d9b2a5e7-7d94-42be-8862-614e556e0497] Should send full result for execution to backend as it has 3 results. Status: EXECUTING
shuffle-workers.1.gn5ikdzc41ak@soar-worker-01    | 2024/03/13 06:01:12 [DEBUG][d9b2a5e7-7d94-42be-8862-614e556e0497] NEWRESP (from backend): {"success": true, "reason": "success"}

[frikky]

@0x0elliot status?