Hello all,
I can’t understand why a BEWF is not showing in my server logs. The workflow lauching the back-end WF is visible and stated as finished in the logs, and the BEWF seems to work because I can see a scheduled WF in the scheduler - that is one of the steps of the BEWF.
I’ve checked every case in the logs parameters, and it doesn’t appear.
I’m working on the mobile 
editor and launching the wf through the preview of the app on Bubble Go, could that be related?
Hey! @manon.guerriersup this can definitely be confusing, but what you’re seeing is actually expected behavior. When a backend workflow is triggered from the mobile editor / Bubble Go preview, it doesn’t always show up as its own entry in the server logs. You’ll usually only see the workflow that scheduled it, not the BEWF itself.
Since you can see the scheduled workflow in the scheduler and it’s running, that confirms the BEWF is firing correctly. It’s more of a logging limitation than a workflow issue.
If you want to doublecheck, try triggering the same backend workflow from the web preview or live app and you should see it appear normally in the logs.
What?
I just wanted to confirm that it’s a logging limitation in Bubble Go and not an issue with the workflow itself. Thanks!
Thanks for the feedback, though it is not very practical when one wants to debug a BEWF… but it is good to know I can stop searching 
Yes, this is very likely related to how you’re triggering it, and you’re not missing something obvious 
A couple of things to clear up first. Backend workflows don’t always appear in the server logs the way you expect, especially when they’re triggered indirectly. If your front-end or another workflow is calling the BEWF and that step shows as “finished”, Bubble considers its job done — it doesn’t guarantee you’ll see a separate, clean log entry for the BEWF itself.
The biggest clue in your case is this part: you’re triggering it from the mobile editor via Bubble Go. Bubble Go preview is a bit special. It doesn’t behave exactly like web preview or Live, and server logs can be incomplete or misleading when workflows are triggered from there. It’s very common to see:
the calling workflow logged,
scheduled workflows appearing in the scheduler,
but no visible BEWF entry in server logs.
Since you can see the scheduled workflow in the scheduler, that means the BEWF is running. The absence in logs is more of a logging/preview limitation than a logic problem.
A few practical checks:
Try triggering the same flow from web preview or Live and check logs again — you’ll usually see it appear.
Make sure you’re looking at the correct environment (Live vs Dev) in the logs.
Remember that scheduled steps may log separately from the BEWF that scheduled them.
I trigged it from the web app and got the logs complet this time ! thanks for the help
Great
