# Server log issue (Oct 20)

**URL:** <https://forum.bubble.io/t/server-log-issue-oct-20/383534>\
**Category:** Need help\
**Created:** [October 20, 2025, 11:39am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534 "2025-10-20T11:39:12Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![rpetribu](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/rpetribu/32/90852_2.png) [@rpetribu](https://forum.bubble.io/u/rpetribu)\
**Post date:** [October 20, 2025, 11:39am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/1 "2025-10-20T11:39:12Z")

</div>

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:

1. I’m testing in the **development** environment, so there’s no other noise in the log besides my own entries.
2. All the **Advanced** checkboxes are enabled.
3. 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.

Can anyone test this on their end?

---

<div class="post-metadata">

**Author:** ![boston85719](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/boston85719/32/77286_2.png) [@boston85719](https://forum.bubble.io/u/boston85719)\
**Post date:** [October 20, 2025, 11:41am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/2 "2025-10-20T11:41:00Z")

</div>

What is a Console Log server action?

---

<div class="post-metadata">

**Author:** ![rpetribu](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/rpetribu/32/90852_2.png) [@rpetribu](https://forum.bubble.io/u/rpetribu)\
**Post date:** [October 20, 2025, 11:45am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/3 "2025-10-20T11:45:50Z")

</div>

Good 😅

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.

---

<div class="post-metadata">

**Author:** ![boston85719](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/boston85719/32/77286_2.png) [@boston85719](https://forum.bubble.io/u/boston85719)\
**Post date:** [October 21, 2025, 2:58am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/4 "2025-10-21T02:58:13Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![asked111](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/asked111/32/210876_2.png) [@asked111](https://forum.bubble.io/u/asked111)\
**Post date:** [October 21, 2025, 6:31am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/5 "2025-10-21T06:31:48Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ed19](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ed19/32/193092_2.png) [@ed19](https://forum.bubble.io/u/ed19)\
**Post date:** [October 21, 2025, 12:43pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/6 "2025-10-21T12:43:19Z")

</div>

A couple of backend workflows not showing for me at all either, really frustrating to debug.

---

<div class="post-metadata">

**Author:** ![rpetribu](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/rpetribu/32/90852_2.png) [@rpetribu](https://forum.bubble.io/u/rpetribu)\
**Post date:** [October 21, 2025, 12:52pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/7 "2025-10-21T12:52:26Z")

</div>

> [@boston85719](#):
>
> Have you tried creating a DB entry as your own log

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…

---

<div class="post-metadata">

**Author:** ![nico.dicagno](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/nico.dicagno/32/207961_2.png) [@nico.dicagno](https://forum.bubble.io/u/nico.dicagno)\
**Post date:** [October 21, 2025, 3:57pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/8 "2025-10-21T15:57:12Z")

</div>

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.

> [@rpetribu](#):
>
> 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 😵‍💫.

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.

---

<div class="post-metadata">

**Author:** ![ed19](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/ed19/32/193092_2.png) [@ed19](https://forum.bubble.io/u/ed19)\
**Post date:** [October 21, 2025, 4:41pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/9 "2025-10-21T16:41:26Z")

</div>

Spent 3 hours today trying to figure out something that was incredibly simple to fix, all I needed was to be able to see what/where it was 😑

---

<div class="post-metadata">

**Author:** ![rvanrooyen](https://avatars.discourse-cdn.com/v4/letter/r/b5ac83/32.png) [@rvanrooyen](https://forum.bubble.io/u/rvanrooyen)\
**Post date:** [October 21, 2025, 5:02pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/10 "2025-10-21T17:02:44Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![rpetribu](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/rpetribu/32/90852_2.png) [@rpetribu](https://forum.bubble.io/u/rpetribu)\
**Post date:** [October 21, 2025, 6:05pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/11 "2025-10-21T18:05:55Z")

</div>

> [@nico.dicagno](#):
>
> To be fair creating custom server logging is quite standard practice in conventional dev environments

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.

> [@nico.dicagno](#):
>
> Bubble should absolutely be providing better logs considering it is a No/LowCode ecosystem.

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.

---

<div class="post-metadata">

**Author:** ![scott23](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@scott23](https://forum.bubble.io/u/scott23)\
**Post date:** [October 21, 2025, 6:24pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/12 "2025-10-21T18:24:31Z")

</div>

Ditto here. Have you submitted a bug? I’m about to.

---

<div class="post-metadata">

**Author:** ![alastairgwatson](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/alastairgwatson/32/212095_2.png) [@alastairgwatson](https://forum.bubble.io/u/alastairgwatson)\
**Post date:** [October 21, 2025, 7:02pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/13 "2025-10-21T19:02:32Z")

</div>

There’s defo something wrong with the logs. Making it impossible to see what the issues are with the application.

---

<div class="post-metadata">

**Author:** ![rpetribu](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/rpetribu/32/90852_2.png) [@rpetribu](https://forum.bubble.io/u/rpetribu)\
**Post date:** [October 21, 2025, 7:37pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/14 "2025-10-21T19:37:37Z")

</div>

> [@scott23](#):
>
> Ditto here. Have you submitted a bug? I’m about to.

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.

---

<div class="post-metadata">

**Author:** ![alastairgwatson](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/alastairgwatson/32/212095_2.png) [@alastairgwatson](https://forum.bubble.io/u/alastairgwatson)\
**Post date:** [October 21, 2025, 7:42pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/15 "2025-10-21T19:42:53Z")

</div>

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.

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/c/7/c7effa32f42dec5179fb663bee7ee59df849f876.png)

---

<div class="post-metadata">

**Author:** ![rpetribu](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/rpetribu/32/90852_2.png) [@rpetribu](https://forum.bubble.io/u/rpetribu)\
**Post date:** [October 21, 2025, 7:43pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/16 "2025-10-21T19:43:42Z")

</div>

Nice! I will do the same

---

<div class="post-metadata">

**Author:** ![scott23](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@scott23](https://forum.bubble.io/u/scott23)\
**Post date:** [October 22, 2025, 3:39am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/17 "2025-10-22T03:39:17Z")

</div>

I opened one as well and got a copy paste response to what Alastair received.

Unclear on priority, but seems to be something they’re aware of 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![gerbertdelangen](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/gerbertdelangen/32/144602_2.png) [@gerbertdelangen](https://forum.bubble.io/u/gerbertdelangen)\
**Post date:** [October 22, 2025, 7:50am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/18 "2025-10-22T07:50:38Z")

</div>

Yes, same here, steps missing from the log.

---

<div class="post-metadata">

**Author:** ![alastairgwatson](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/alastairgwatson/32/212095_2.png) [@alastairgwatson](https://forum.bubble.io/u/alastairgwatson)\
**Post date:** [October 22, 2025, 8:00am UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/19 "2025-10-22T08:00:39Z")

</div>

@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

---

<div class="post-metadata">

**Author:** ![scott23](https://avatars.discourse-cdn.com/v4/letter/s/ccd318/32.png) [@scott23](https://forum.bubble.io/u/scott23)\
**Post date:** [October 22, 2025, 2:49pm UTC](https://forum.bubble.io/t/server-log-issue-oct-20/383534/20 "2025-10-22T14:49:05Z")

</div>

Got an update to the ticket that they’ve pushed a fix, haven’t had a chance to test yet, but hoping it’s fixed for you all.

[Next page](https://forum.bubble.io/t/server-log-issue-oct-20/383534.md?page=2)
