Guys, something seems off with the Server log. Since this morning, I’ve been trying to track the execution of some tasks, and I’ve noticed that certain entries that should be visible in the Server log simply don’t show up.
To test it, I created a backend workflow with a simple Console Log (Server) action just to see if the text would appear — and nothing.
The log shows that a task was scheduled successfully, but that’s it… no log message appears.
Before anyone asks:
I’m testing in the development environment, so there’s no other noise in the log besides my own entries.
All the Advanced checkboxes are enabled.
The flow is simple — I click a button, it schedules a backend workflow for “now,” and that backend workflow contains a Console Log (Server) with some sample text.
It’s an action from a plugin called Ultimate Toolkit, which allows you to write information to the server-side log. This is often very useful for validating specific steps in backend workflows. I use it regularly across several backend workflows — it really helps me audit information quickly.
It works just like the console log we use in the browser, but the information gets recorded in Bubble’s server logs instead.
Have you tried creating a DB entry as your own log, run the plugin action after create DB thing and then check if the logs are working? I imagine if there is a bug, bubble support will want you to rule out it’s not the plugin.
I also had this issue a few days ago (and possibly still) ran a recursive scheduled API workflow over 1600 items, modifying them individually, but I could not find anything I expected to find on the logs whatsoever.
This is the kind of workaround only Bubble users have to do
Yeah, I thought about that possibility too, but honestly, it felt too humiliating, even knowing no one would actually see it .
The workflow itself is working perfectly — the issue is that more than half of the steps just don’t show up in the log anymore. This started about two days ago. Super frustrating.
Doing a proper audit through Bubble’s logs is already a nightmare, and now with missing entries, it’s even worse…
I’ll try to set aside some time (and courage) to open a support ticket soon…
Yeah I’m also getting very limited Server Logs on apps, the vast majority of loggable actions are just not there - and I see 0 server logs from Unauthenticated Users.
Wish me luck debugging.
To be fair creating custom server logging is quite standard practice in conventional dev environments - but Bubble should absolutely be providing better logs considering it is a No/LowCode ecosystem. And aside from that, creating proper Server Logs wouldn’t exactly be free as they would consume crazy WU.
Same here. We did a major release on Sunday to accommodate a new division. Followed by an extensive setup/config . We had some issues so I was in the log all day long. The problem started around 3pm central. log entries started disappearing at that time. Ex. Front end sets a field that the backend picks-up on a db trigger and kick off a process that create nearly 100 logs entries. Could see the frontend logs up too the trigger set. NON of the backend entries was showing and yet the backend part completed. I also have a self-reloading scheduled task that maintains a JWT. The connection is fine, so I know JWT maint is running and jet I can’t find any log entries any more.
No no… I think I wasn’t clear in my previous response. I actually have several places where logs are stored — they’re important for tracking some of our events.
What I meant in my reply was the need to create a database to track each step of the backend events, so I could identify at which point the error was happening.
That’s what I eventually had to do to pinpoint where the issue was occurring.
Have you ever had the chance to see how n8n stores its execution logs? If I’m not mistaken, other platforms like Make and Zapier do it in a similar way — with visual information of each step, showing the inputs and outputs of every node…
It even lets you filter by date or any other relevant information, which is fantastic. Every time I need to audit an error in one of my n8n automations, I can do it in under a minute, because I know exactly where, when, and why the error happened.
I haven’t opened a bug report yet — honestly, I find the whole process a bit tedious, and it usually takes quite a while to get a response. Before doing that, I just wanted to make sure it wasn’t something specific to my setup.
At least now, with everyone else’s comments, it helps confirm that the problem is real, and I can even include a link to this thread in the support ticket.
But yes, I’ll go ahead and open the ticket and keep everyone posted.
I’ve opened a bug report and got this reply - so there is an issue, and it’s known. I was under the impression that the status page was now going to be updated more frequently to avoid this exact situation, where people spend time trying to fix things only to find out there are issues on the platform. Sigh.
@fede.bubble - can we get some clarity on what’s going on? Is this impacting workflows actually running? I have workflows that worked yesterday and now they just seem to be stopping halfway through running and nothing is appearing in the logs to assist
.
