Flow stuck in In-progress status

Hi there,

We have some flow runs that stuck in “In-progress” status. What can we do to let it continue running? Thanks!

In the flow chart of the run, seems it is stuck in a run code step. However below section show that the run code step is finished successfully.

Peter

The UI says the run code step is finished successfully.

I suspect because the run code step return value with incorrect type like below. However I cannot reproduce it in another test store.

// Say foobar is int
type Output {
  foobar: Int!
}

// Return a number string in code
return {
  foobar: "100"
}

1 Like

Not sure without seeing the workflow run. Sometimes it appears stuck but actually already finished because of the order in which our run page read the data.

1 Like

Found the thread through google, bumping since I have to runs from yesterday still “stuck” at “Order fulfilled”.

I’ve tried to disable and re-enable the workflow, and also tried to trigger another run. New runs are also stuck on the trigger.

It seems to be workflow (or trigger?) specific.

I found the error.

One of my ‘Run code’ actions had jsonValue as a requested property on metafields. Removing that made the flow run.

Don’t loop over metafields like this. Instead you can access each metafield individually, which potentially saves you costly API calls. You can’t add a metafield in Run code, but you can add one every other place there is an “Add a variable” link

1 Like

Oh lol ofcourse - I did not think this was a possibility

which is simply an alias made from previous conditional step :brain:

1 Like