Hey team, we’ve had a couple of instances where Flow nodes will appear to be in ‘Draft’ mode when inspecting the Flow run.
When this happens, the node appears to have succeeded but no actual action is taken:
Is there some documentation around what is going on here/how to address and how to avoid this from happening in the future?
CC @keiraarts
Hi, I think you are seeing draft tasks from your partner account there. So likely you need to edit the workflow to remove that draft task and instead use the published version.
Thanks @paul_n
Cc @keiraarts
Sorry if I’m being daft here but what is a draft task?
How do we know if an action is in draft when building flows.
Also @keiraarts can you confirm these nodes worked previously?
Just want to pinpoint if they have somehow been thrown into draft based on something we’ve done?
We had this happen with another action previously and it seemed to be limited to a single store (it was our reverse unpaid edits action).
Since you are developing your own tasks, you will have some that are available only in your dev shops and others that come from Flow as published tasks. I think you have accidentally used some of the prior (“Draft tasks”) in your workflows, possibly by copying from one shop to another somehow.
Here’s what I see in my instance of Flow https://screenshot.click/09-26-1smdg-h1nsw.png
But I suspect that the Draft badge is only for the Flow team. You may instead see 2 tasks in your task picker?
I’ve gone ahead and removed that task and then re-added it. There weren’t two tasks in the task picker.
We’ll keep an eye on it.
But to be clear, are you saying that if we create a flow in our test store (dev store) and then export it and re-import it to a prod store, there is a chance some of the task/action nodes may be being copied over in draft mode?
I couldn’t see any in a draft state on our dev store so like you said, it might just be something your team can see:
Or could it be the flow we created a while ago is using an action node that has since been updated and those nodes don’t update automatically?
CC @keiraarts
Yeah, I think that would happen if you created a workflow while running app dev with a trigger/action that we updated by app dev.
