Forum Discussion
BradLemke
3 years agoQrew Assistant Captain
It looks like your automation fires on either Add or Modify, but your Pipeline is set up for Modify only. Other than that, this looks perfect.
------------------------------
Brad Lemke
------------------------------
------------------------------
Brad Lemke
------------------------------
- SimonH3 years agoQrew CadetI made the same mistake when first starting with pipelines.
To get a pipeline to trigger on Edit and Insert you need to use the "On New Event" trigger
and select both On Add and On Modify
------------------------------
Simon H
------------------------------- MarkShnier__You3 years agoQrew ChampionJust to echo what has been said above. I now I'll try to start all my Triggers on new event because you never know when you have to circle back later and change the trigger and as you know with pipelines we can't change previous steps or the trigger once they're built. So if you start a new event then you have flexibility if they need to change in the future.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------- SimonH3 years agoQrew CadetThanks for that tip Mark, I'll probably start doing the same moving forward.
In the past if I needed to change a trigger I would create a temporary Pipeline with just the trigger defined.
Then export the YAML from both pipelines and swap the trigger step and re-import.
For many updates it is as simple as that. If you are coming from a manual trigger though then you may have to increment all the pipeline step letters, which might still be easier then rebuilding the entire pipeline
------------------------------
Simon H
------------------------------