Execution History Disappears before EXECUTIONS_DATA_MAX_AGE

Questions
1

Describe the problem/error/question

Workflows have execution history that disappears in less than a day. Here’s how I have the following environment variables set:
EXECUTIONS_DATA_PRUNE=“true”
EXECUTIONS_DATA_MAX_AGE=“700”

Information on your n8n setup

  • n8n version: 1.25.1
  • Database (default: SQLite): postgresql
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: Ubuntu 20.0.4
2

Hey @jhambach,

Has it always been set to 700?

3

Yes we’ve had it that way for awhile (pre v1.0) just so we can look at executions from the past couple months. For some reason it seems like execution history isn’t even saving for more than 24 hours

4

That is very unusual, Is it all workflows or just a few?

5

Looks like for all workflows. The time that it’s dropping the history is really weird. It’s currently 1:03PM CST here, and I can only see executions back to 6:31AM CST.

6

Hey @jhambach,

That is unusual, How manu total execution runs are there? I know we do have a default limit of a few thousand. Can you try updating as well?

I am also curious, What timezone do you have your n8n instance set to?

7

Ah I think that may have been the issue, I didn’t realize that the EXECUTIONS_DATA_PRUNE_MAX_COUNT defaulted to 10000. I changed that to 0.

Our GENERIC_TIMEZONE is America/Chicago. I’ll monitor and see what happens today. Thanks for your help

8

Hey @jhambach,

That prune count one could be the one then if you have that many :slight_smile:

1 Like
9

That was the problem, since I’ve changed it I can see the full history now. Thank you!!!

10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.