{"version":"2.1.239","anchor":"workflow-v2-run-handles-are-scaffolded-but-never-created","canonical_anchor":"workflow-v2-run-handles-are-scaffolded-but-never-created","heading":"Workflow \"v2 run\" handles are scaffolded but never created","tier":"soon","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/workflow-v2-run-handles-are-scaffolded-but-never-created","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Workflow \"v2 run\" handles are scaffolded but never created\n\nWorkflow records can hold a newer run handle, but nothing ever creates one here.\n\n**What**\n\nWorkflow task records can now hold a v2 run handle that gets killed when the workflow is stopped, and the workflow tool's output schema is meant to absorb extra fields from a provider. That provider compiles to a bare `return;`, so no extra fields are added and no v2 run is ever created here.\n\n**Evidence**\n\n`runOpOutputFields`\n\n- Area: Workflows\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}