This is blocking deployment from CI → intg/stge/prod environments.

Hi all,

I’m using CircleCI dynamic config (setup: true + continuation orb) and facing an issue where tag-triggered pipelines show:

“No workflow” after setup phase, even though continuation returns successfully.

Setup:

• setup: true config with continuation/continue
• Passing parameters via JSON (/tmp/continue-params.json)
• Tag-based deployments (ci-*, rc-*, r-*)
• Using when: in continuation config:when: matches: pattern: "^ci-.*" value: << pipeline.parameters.pipeline_tag >>

What I’ve verified:

• $CIRCLE_TAG is available in setup job
• JSON file is written and passed to continuation
• continuation step completes successfully
• workflows exist in continue_config.yml

Issue:

• Tag pipeline shows: → Setup job runs → continuation succeeds → No workflow is selected

Question:

• Do tag contexts need to be explicitly preserved differently in dynamic config?
• Is there a known issue with pipeline.git.tag or parameter passing for tag-triggered pipelines?

Would really appreciate any insights, especially from folks using dynamic config with tag-based deployments.

Thanks!