Hello,
there are only a few posts about this kind of error and more or less all of them seem to be related to the legacy plans. I am on the WU plan and have never had this before. It took me several hours to actually find this:
The workflow is the last step of a chained workflow on a list workflow-operation. I don’t think that the 5 minute timeout could have caused this since the steps inside this workflow include an api call to openai and a few changes to things inside the database. Nothing heavy. OpenAi did not have a timeout or error while processing the call.
There was not notification via email and the support I have contacted will look into it. How do you guys handle this kind of situation and monitor it?
Thank you!
Use the condition : if error occurred while running this workflow > do this,
It may be a display simple pop up which may say try again
Thank you @siddharth but this option does not exist. Or maybe I am overseeing something and you can point me where I can find this option.
For clarification: I am talking about the backend.
If bubble does not send out notifications I kind of have to do it myself I guess. But how catch this kind of error is a big question for me.
Thanks again!
i was talking about this, not available on backend wf
I have seen this on the WU plan also. And similarly, it took me ages to track it down in the logs.
What I think “fixed” the issue for me (or sidestepped more accurately) was I had two things occurring on the hour, a web hook coming in that caused a lot of processing (lots of database inserts) and something that sent a lot of emails (with lots of database reads).
I could easily change the timing of the email job, and easily put in the hacky “wait X seconds between workflows” with the email processing. So I did that.
And the database writes were unavoidable … but I could generally optimise not writing unused columns.
I was on a “reduce all WU” at the time so I can’t point to any single thing …
But it was painful that for Backend Worflows - these failures are silent unless you go looking in the logs. For a while, I had this screen permanently open …
So no decent answer - just I feel your pain 
Do you know what the operation was?
Thank you @lindsay_knowcode shared pain is half pain or how is the saying … 
@boston85719 hi, the logs point to a specific workflow but not to the action or step.
I have contacted the support and can expect an answer by tomorrow since bubble is currently short staffed…
What is the setup of that workflow and how is it triggered? Sharing screen shots helps.
So the support has told me that this was triggered by a hard limit and that there is absolutely no way to know when this happens.
It would be really helpful if many people could vote for this on the idea board: Be able to catch a backend workflow timing out | Bubble
Thank you!
