Why Can't I Merge My Edited Cron Trigger Flow to Production in V3?

1

This topic was automatically generated from Slack. You can find the original thread here.

So speaking of V3, I am seeing a bug I saw before, and I honestly don’t remember what the resolution was - sorry. My flow has a cron trigger. I edited it from 4 hours to 3, and saved. I can’t merge to production. It’s like the change to configuration of a trigger isn’t… a real change?

2

Oh, interesting. Do you mean the Merge to production button is disabled?

3

nod. im sure if i go into a code step, add a space, and save, it will fix it

4

should i do so, and this msg is enough for yall, or wait and let you inspect?

5

Yea that’s plenty, I’ll try to repro in a bit, but I have a suspicion I might know what’s happening. And yea, the change in a code step will probably work around the issue, I agree.

6

Thanks for flagging!

7

np

8

fyi, the workflow (its on bluesky as well) - Dragon Hoards (@dragonhoards@botsin.space) - botsin.space

9

Chatting with eng, and I realized that technically any change you make to the trigger will get deployed immediately, even if you don’t merge to production via Git sync, since the trigger is an independent resource from the workflow

10

It’s still a bug that we should address, but just FYI

11

interesting. and now its vaguely coming back to me when i saw this last time