Workflow chat: model doesn't understand edges

[josephjclark]

This generated workflow is invalid:

The Consolidate All Data step thinks it'll run when both its parent steps have completed.

While this is a feature we'd like some day, it's not how it works! Every edge is executed simultaneously with no waiting.

We should update the prompt to be a little more clear/strict on this

[taylordowns2000]

hey @josephjclark and @hanna-paasivirta , a quick note here (maybe just language nitpicking, but i think it's important for the AI)...

the generated workflow there IS perfectly valid. the problem, however, is that it doesn't do what the chat thinks it does.

This is a really nice example of a workflow with multiple paths to a downstream node. Usually, these multiple paths are organized with some sort of exclusive logic (either go down path A or fo down path B) but it's totally fine to say "go down both paths".

The result of this workflow run will be that steps 4, 5, 6, 7, and 8 will each be run twice assuming those first 3 steps succeed. That's weird, but totally valid. The trouble is that the AI chat thinks steps 4, 5, 6, 7, and 8 will only be run once... with step 4 waiting until both steps 2 and 3 finish and their final states are (somehow) merged.