Worker failing to invoke Workflow with no useful debug information
I have a really bizarre issue that I have tried my best to solve on my own, but ultimately I think I need someone with Cloudflare to help.
I have a worker that's bound to a workflow that's been working fine for over a week. Out of nowhere seemingly it's stopped working. Specifically when the worker goes to call the workflow it fails with a super non-helpful "500 Error: internal error". I've tried deleting the worker and redeploying it. Nothing. I've tried changing the workflow name and redoing the binding. Nothing.
I think the issue could maybe be the binding somehow, but if I completely remove the binding from the TOML then I get a different type of error that is saying create is not defined, which seems expected. I've tried invoking the workflow through the UI and it works fine. It just seems to be a binding issue.
My only lead is that I think this may have happened when I started to work on binding the workflow cross script to a different worker. However I removed this binding and things still aren't working. I really need some help debugging this as there's several weeks worth of work tied up in that workflow and the error message on our end is useless. Can someone help lookup a better error because all I get right now if I wrap the invoking in a try catch is the error shared above, which is not helpful.
I have a worker that's bound to a workflow that's been working fine for over a week. Out of nowhere seemingly it's stopped working. Specifically when the worker goes to call the workflow it fails with a super non-helpful "500 Error: internal error". I've tried deleting the worker and redeploying it. Nothing. I've tried changing the workflow name and redoing the binding. Nothing.
I think the issue could maybe be the binding somehow, but if I completely remove the binding from the TOML then I get a different type of error that is saying create is not defined, which seems expected. I've tried invoking the workflow through the UI and it works fine. It just seems to be a binding issue.
My only lead is that I think this may have happened when I started to work on binding the workflow cross script to a different worker. However I removed this binding and things still aren't working. I really need some help debugging this as there's several weeks worth of work tied up in that workflow and the error message on our end is useless. Can someone help lookup a better error because all I get right now if I wrap the invoking in a try catch is the error shared above, which is not helpful.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
