How to overcome the overriding of the timestamp of workflow

Questions
1

Describe the problem/error/question

Hi
my one workflow lastexcution time override the other workflow time.

When I run it for one workflow for the first time the value should be

  • executionTimeStamp: 2023-04-26T12:11:43.398Z
  • lastExecution: 1990-01-01T00:00:00.000Z
    BUT
  • executionTimeStamp: 2023-04-26T12:11:43.398Z
  • lastExecution: 2023-04-26T12:11:42.398Z ( it’s fetching the value from the another workflow last execution)

is it possible to have the last execution based on the workflow specific not global.

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • **n8n version:0.222.0
  • **Database (default: SQLite):latest
  • **n8n EXECUTIONS_PROCESS setting (default: own, main):own
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):docker
  • **Operating system:MAC
2

@Gouravdev is this the same as your other question with the static data?

3

@Jon its clear now thanks n8n team for the help.

4

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