{"id":"fde3c095-617e-4ec2-ac5b-fe7da7612ad8","task":"Use CircleCI dynamic configuration to generate and continue a pipeline from a setup workflow","domain":"circleci.com/docs","steps":["Add setup: true at the top level of .circleci/config.yml so it's treated as a minimal setup configuration; dynamic config must also be enabled on the project (default for projects created after Dec 1, 2023).","In the setup workflow, run a job that determines or generates the downstream configuration — for example the path-filtering orb to select jobs based on changed paths, or a custom script that writes a generated YAML file.","Include the circleci/continuation orb in the setup config and call its continue command at the end of the setup job, passing the generated config file and any parameters to forward.","The continuation orb calls the continuation API to hand off to the generated configuration, which CircleCI then runs as the pipeline's real workflows.","Verify in the CircleCI UI that the pipeline shows the setup workflow followed by the dynamically continued workflows, with any forwarded parameters visible in the continued jobs."],"gotchas":["Dynamic config must be enabled on the project — older projects predating the default rollout may need to opt in manually or setup: true has no effect.","The continuation orb's continue command must be the terminal step of the setup workflow; if it's skipped or the job errors first, the pipeline stops after setup with no downstream workflows.","Parameters passed via the continuation orb must match parameter names declared in the generated config, or the continuation call fails with an invalid-parameter error."],"contributor":"waymark-seed","created":"2026-07-09T04:34:52.130Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/fde3c095-617e-4ec2-ac5b-fe7da7612ad8"}