Can't Access Executions History

Questions
#1

Hi

Not sure exactly when this started but I am unable to view any execution history for my workflows. Either via the individual workflow executions link or executions link from the left side bar - it’s just blank - but we’ve been running workflows for months so it should be showing lots of entries:

image
image2412×726 34.4 KB

I’ve tried updating to the latest release (Version 0.219.1) but no change,.
We run n8n hosted on digital ocean / docker droplet.

Any help appreciated.

#2

Quick update on this. looks like there’s something hammering the DO resources causing the application to run extremely slow. I’ve reverted to an earlier snapshot but to no avail.

Update:
After testing, it seems that when I select “Executions” either from the individual workflow list or the main list of executions in the left panel the server disk read activity increases and is sustained which causes the application to become extremely slow/not responsive. Not sure if you can help identify why it’s just started doing this though?

image
image873×273 18.9 KB

#3

Hey @mbuk,

Which database are you using? If it is the default sqlite one how large is it?

#4

Hi jon
Yeah standard install as per Digital Ocean - n8n Documentation
Looks like we needed to prune executions time and volume.
Ideally though we don’t want to have to do this. I’ve contacted the enterprise team…

#5

Hey @mbuk,

That will do it, So it might be worth moving to a different database which wouldn’t have that same impact on the disk (assuming a different service).

#6

Yeah and the ability to have Db access would also be good

1 Like
#7

@Jon I’m just testing a new install. It looks like I can define to use mysql in the .env file which I’ve done. Do I also need to add something into docker-compose.yml file in order to utilise the mysql database defined in the .env file? Looks like the application is still using sqlite

#8

Hey @mbuk,

You would need to set the environment options we require for the database, You can find them in our docs here: Supported databases and settings - n8n Documentation

#9

@Jon added to .env
I’m now getting ERR_TOO_MANY_REDIRECTS when trying to access the subdomain that n8n resides on.
We use cloudflare. Proxy is disabled. Any ideas?

edit: now getting a 502 error.

#10

Hey @mbuk,

Without seeing your full config it is hard to say.