Issue with "Draft" trigger after migrating Flow extensions to CLI

Hello devs,

I have recently migrated some Flow extensions to be managed via the CLI. I just noticed today, when searching for the the trigger within Flow, two results are shown for the trigger, one of which has a (Draft) badge. In my extension only app, there is only one Flow extension defined.

Can you advise what has caused and how to remove the draft without impacting any existing Flows?

Thank you

Hey @daryl

DMing you for more details.

Update: this does appear to be a bug isolated to dev stores, where duplicate triggers are appearing. We have a fix in the works to resolve this. Will share another update when this is in production.

Ok thanks for the update!