We’re using CircleCI setup/continuation with tags enabled:
-
config.yml uses setup: true and circleci/continuation@2.0.1.
-
The only job in the setup pipeline is trigger-continuation, which calls continuation/continue with continue_config.yml.
-
The setup workflow runs for all tags (tags: only: /.+/).
The continued config is minimal and always-on:
-
continue_config.yml contains a debug_continuation_pipeline workflow that should always run.
-
This workflow only echoes pipeline context and environment variables.
Observed behavior:
- For tag pipelines, the setup workflow runs and continuation/continue completes successfully.
- The continued pipeline never appears (no debug_continuation_pipeline jobs run).
Expected behavior:
- A continuation pipeline should be created for tag-triggered setup pipelines, and debug_continuation_pipeline should run.
Important: The exact same setup works when triggered by a branch push (the continuation pipeline is created and debug_continuation_pipeline runs). The issue only happens for tag-triggered pipelines. And we’ve been able to have it working a couple of weeks ago.
When triggered by a tag: https://app.circleci.com/pipelines/github/yappbox/monotonic/2298/workflows/e470be73-1bb7-4f5a-ad55-72aa8838654d
When triggered by a branch: https://app.circleci.com/pipelines/github/yappbox/monotonic/2299/workflows/55958c92-bc7b-40ef-9972-879fb207849d
This suggests a bug with continuation + tags (continuation request accepted but no child pipeline created). If this is expected, please point to documentation; otherwise we’d like this investigated.