Hope you’re both well!
Not sure if this one is already across your desks but I was editing a large Flow for a merchant today and came across some recurring bugs.
Recorded some replication steps here:
@kalen is this something you’ve also been running into recently?
Thanks as always team 
This looks to be caused by the workflow taking a while to save the change that you made (adding a new condition). In normal cases adding the condition will pop open the condition panel on its own almost immediately, but here you are clicking on the condition before that happens which appears to trigger the issue. While not a great solution, if you wait for the configuration panel to pop open on its own (which, I also want to note, it correlated with the “saving” spinner appearing at the top right), then you should be able to edit it without the issues you were experiencing.
In the meantime I’ll raise this issue with the team and see if we can dig into either why it takes so long to save this workflow, or if we can make a change so that you can still edit when this happens.
What’s the tldr on that video? I don’t have a lot of flows that big btw - that may be why.
Thanks Tim, yeah that make sense. Most likely due to the size of the Flow I’d expect. Thanks for taking a look and seeing if you can dig into it further too!
Yeah definitely contributing.
We were just getting 2-3x GraphQL fetch errors and then no way to add conditions as the panel hadn’t loaded any options.
We also were seeing it take a long time for the ‘Review’ notification to go away
Slowing down helped get through it all.
And yes, was definitely due to the size of the Flow I expect.
Thanks for the video. I know the lag is not ideal here.
If you have the chance to refactor that workflow, I wonder if you could use metaobject entries as a lookup table for your SKU/Tag combinations. Then the workflow would look something like this:
This is great thanks @paul_n. I’ve not yet had the chance to do a metaobject entries Flow so this would definitely be a good use case to try.
Yeah I think the wait after last item would be fine in this case. Thank you again!
