# N8n Blank Errors

**URL:** <https://community.n8n.io/t/n8n-blank-errors/118304>\
**Category:** Feedback\
**Tags:** core\
**Created:** [May 21, 2025, 3:29am UTC](https://community.n8n.io/t/n8n-blank-errors/118304 "2025-05-21T03:29:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Learned](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/andrew_learned/32/46049_2.png) [@Andrew\_Learned](https://community.n8n.io/u/Andrew_Learned)\
**Post date:** [May 21, 2025, 3:29am UTC](https://community.n8n.io/t/n8n-blank-errors/118304/1 "2025-05-21T03:29:08Z")

</div>

Overall, I love this product! I self-host so this may be on my Google Cloud setup, but after working with n8n for about 6-months now I wanted to report back my #1 frustration with it - errors that don’t indicate what caused the error.

I’m not sure if I’m alone here, but on complex workflows, I often times get an error on the execution, but when I open it up no nodes are red or indicate where the error took place. It’s incredibly frustrating as it doesn’t allow me to troubleshoot the error.

I’ve struggled with how to work this over the weeks and months, but I think it’s isolated to when the server may be overloaded or something… but I’m really not sure because I don’t get any of those errors in n8n obviously.

Has anyone else experienced this? I’m self-hosted on GCP using Kubernetes Instance. # Debug info

## core

- n8nVersion: 1.91.3
- platform: docker (self-hosted)
- nodeJsVersion: 20.19.0
- database: postgres
- executionMode: regular
- concurrency: -1
- license: enterprise (production)

## storage

- success: all
- error: all
- progress: false
- manual: true
- binaryMode: memory

## pruning

- enabled: true
- maxAge: 336 hours
- maxCount: 10000 executions

## client

- userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/136.0.0.0 safari/537.36
- isTouchDevice: false

Generated at: 2025-05-21T03:28:10.734Z

---

<div class="post-metadata">

**Author:** ![Ahmed\_Hossam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/ahmed_hossam/32/95406_2.png) [@Ahmed\_Hossam](https://community.n8n.io/u/Ahmed_Hossam)\
**Post date:** [June 30, 2025, 1:10pm UTC](https://community.n8n.io/t/n8n-blank-errors/118304/2 "2025-06-30T13:10:54Z")

</div>

did find a solution?  
facing same issue here

---

<div class="post-metadata">

**Author:** ![Andrew\_Learned](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/andrew_learned/32/46049_2.png) [@Andrew\_Learned](https://community.n8n.io/u/Andrew_Learned)\
**Post date:** [July 13, 2025, 10:46pm UTC](https://community.n8n.io/t/n8n-blank-errors/118304/3 "2025-07-13T22:46:29Z")

</div>

Sorry, just seeing this. Not completely, but what I started doing is adding some intermittent google sheet log points which works for me - at least in dev. So just different checkpoints adding an external log just so I can isolate where we went off the rails better.

I would bet it’s my server being overloaded at times and n8n failing and not knowing why. But still, I’d want to know that…
