Problem
WorkflowDef supports execution config fields in the DSL (for example retry_policy and timeout settings), but these values are not fully propagated into runtime
WorkflowNode configuration during parser/build.
As a result, workflows defined in YAML/JSON can silently lose configured retry behavior and timeout defaults.
- Define a workflow DSL with:
- workflow-level
config.retry_policy and/or config.default_timeout_ms
- optional node-level overrides in
nodes[].config
- Parse via
WorkflowParser::build_with_agents(...).
- Inspect resulting
WorkflowNode.config values or observe runtime behavior.
Current Behavior
Runtime node configuration does not consistently reflect DSL retry/timeout settings end-to-end.
Expected Behavior
- Workflow-level defaults should apply to all nodes unless overridden.
- Node-level retry/timeout settings should override workflow defaults.
- Behavior should be validated with integration-style parser tests from DSL input to runtime node config.
Problem
WorkflowDefsupports execution config fields in the DSL (for exampleretry_policyand timeout settings), but these values are not fully propagated into runtimeWorkflowNodeconfiguration during parser/build.As a result, workflows defined in YAML/JSON can silently lose configured retry behavior and timeout defaults.
config.retry_policyand/orconfig.default_timeout_msnodes[].configWorkflowParser::build_with_agents(...).WorkflowNode.configvalues or observe runtime behavior.Current Behavior
Runtime node configuration does not consistently reflect DSL retry/timeout settings end-to-end.
Expected Behavior