Issues with Release Fulfillment Order/Fulfillment Order Nodes

Hey @paul_n @Dave_McV

Are you guys aware of any issues right now around ‘fulfillmentOrder data not found’ with regards to the ‘release fulfillment order holds’ nodes?

They continue to work on any live flows we have but as soon as we try and edit a live flow with these nodes on them, we get these errors:

CC @kalen in case you’ve seen this too/know of any fixes or workarounds we can try?

They should be working. We have an improvement for “For each” coming that could’ve messed up things. Can you send a link to this workflow?

I’m not seeing an error in my shop.

Woops didn’t mean to delete: Here is the flow

https://admin.shopify.com/store/drink-hiyo/apps/flow/editor/0194d343-b460-7d16-993c-0868e4c3f182/0194d929-60fe-7661-b905-2219fccd1acc

I’m not seeing an error in that workflow?

If you try and edit the release fulfillment order node, and re-add it, you get this:

And if you save it you get this:

I’m not sure why, but that “for each” step is messed up. Try deleting it and adding it again.

Unfortunately no luck.

Deleted the for loop and replaced both it and the release fulfilment node and still seeing the issue:

Ahh I have found the issue I think!

It was we were doing as for loop and the then action was another for loop directly after.

Whenever I remove the then action the release fulfilment node works ok.

I’ve added a 10 second wait between the for loops and that seems to have fixed it :raised_hands:

Thanks for jumping in. Deleting the For loop and re-adding was what led me to trying this. Appreciate it.

2 Likes

We’ll fix this soon.

One note - we are working to allow more actions in For each. You’ll notice you can now have more than 1 action per loop, so repeat loops should be much less necessary

Hey @paul_n that’s really good to know, thanks!

Unfortunately we’ve seen some more instability in the For Each Loop node this morning.

Video:

Link:

https://admin.shopify.com/store/1f74d5-3d/apps/flow/overview/0192d4f1-820f-712a-821c-24958c14d57c

Is there anything obvious you can see here that would be causing this? In this example we have a conditional check after the for each loop but this hasn’t been an issue in the past…

Yeah, weird. There is a defect when there are multiple loops over the same list. They are clobbering each other and causing weirdness. Working on a fix.

Should be fixed now.

1 Like