My flows stopped working after updating windmill
I updated windmill today, running on coolify and it appears that many of my flows stopped working. Looks like something to do with package cache or lock file, any pointers on how to proceed?
I am seeing stuff like :
And
25 Replies
esm.sh may have changed the source for those urls and we updated deno to deno 2, so those 2 probably ended up having the lockfile not matching anymore
your best path is to re-generate the lockfiles, you can do this by adding a space character and redeploying your flows/scripts.
Will removing /tmp/windmill/cache also work?
inside the worker container
Thanks for the quick reply by the way!
no the lockfiles are in the db
I tried but it is still failing with the same. I added some comments and spaces to the scripts inside the flow and re-deployed to trigger a regenerate, but didn't seem to help. It seems that it worked directly on a script, but the flow itself is still failing. I also added a new temporary step to the flow to make sure it has changed, but still the same error.
you need to modify every script and inline script that throw that error
the lockfile granularity is at the step level, not the flow level
Hm, I've modified all scripts in this particular flow that i am seeing this on.
and you redeployed the flow?
yes, i hit deploy on the flow after modifying
I'm not sure how but you must have missed a step
Let me double check everything again
I've changed the query script, the get skus, the supabase upsert and also the discord inputs, am i missing something?

I'm seeing this Lock summary, which i assume is something new in windmill, here's a more full screenshot of that:

lockfileVersion 1, that lockfile look old
did you re-deploy the workspace script?
i am doing all of this inside the flow, but should i edit scripts directly and re-deploy them first, and then edit the flow and re-deploy?
you only need to redeploy the script unless you pinned the hash of that script in your flow
in which case you need to unpin it
running test inside that specific script seems to show that it works, but if i hit deploy and run it fails.

it fails with what error?
I also see that info at the bottom, have not tried the nobundling.

adding //nobundling seems to work though
then your flow should work now
Just tested and yes, that made the flow work again.
But this probably doesn't fix the core issue I'm having?
what is your core issue?
If i remove //nobundling i am seeing the original error. But is it ok / should i be using //nobundling I guess is my question.
yes, bun is unable to bundle your script
so it will be slower, but not atrociously slow
and the issue is with bun, you can reproduce with bun build locally
it's a new optimisation, before we didn't bundle on deploy
so yes you can add //nobundling without worrying
Ah thanks! I will try and do some test locally too. This flow just runs once per 30 mins to check for new product changes in woocommerce so should not be any problem then.
Thank you for your time and help! I really appreciate it.