Problem:
When setting up a dynamic configuration with the continuation orb or with the path-filtering orb, you might find that the setup workflow is failing with the "Pipeline is not in setup state" error and the continuation workflow does not get triggered.
Solutions:
Verify if the setup workflow was re-run.
The setup workflow can only successfully trigger the continuation workflow on pipelines that are in a
setupstate, after which it updates the related pipeline’s state tocreated.
Once the pipeline containing the setup workflow has been continued, its state will no longer besetup, hence the error "Pipeline is not in setup state".
If this is the case, please try triggering a new pipeline.Make sure that only one continuation is triggered in the setup workflow.
When using setup workflows, you will only be able to use the continuation API once per pipeline. This means that the setup workflow will only be able to trigger one continuation, any further continuations will fail with the "Pipeline is not in setup state" error.
If you would like to use different continuation config files depending on the paths of changed files, please review our advanced path-filtering scenarios or you could consider using conditional workflows in your continuation config.