Deleted Execution still executing. Loop?

Questions
1

Describe the problem/error/question

I have an cron workflow that checks for new data. If nothing is found, it executes another workflow that deletes that execution.

It was working fine and I don’t know why, but I think that execution entered in some type of loop and I think it also triggered the “delete execution”. Now that execution is executing indefinitely and I cant stop that because the execution was deleted (?)

Sometimes my server load skyrocket and I think that loop is at fault, but now it’s stable with that executions stills running.

I think that could be an issue in the “delete execution” workflow itself.

image

image

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

{
  "meta": {
    "instanceId": "89161416c4a2dc17143e4f98fa4a90a06fe00a8f99c1a12d1a77b368cb99160f"
  },
  "nodes": [
    {
      "parameters": {},
      "id": "02c9849d-1991-4289-8c75-318a18fc3b70",
      "name": "Execute Workflow Trigger",
      "type": "n8n-nodes-base.executeWorkflowTrigger",
      "typeVersion": 1,
      "position": [
        1340,
        460
      ]
    },
    {
      "parameters": {
        "resource": "execution",
        "operation": "delete",
        "executionId": "={{ $node[\"Execute Workflow Trigger\"].json[\"execution_id\"] }}"
      },
      "id": "62f40651-c308-423b-b8a7-7772fdc05f88",
      "name": "n8n1",
      "type": "n8n-nodes-base.n8n",
      "typeVersion": 1,
      "position": [
        1760,
        460
      ],
      "credentials": {
        "n8nApi": {
          "id": "28",
          "name": "n8n account"
        }
      }
    },
    {
      "parameters": {
        "amount": 10,
        "unit": "seconds"
      },
      "id": "962e42b8-3b83-44d6-911f-4a346dc04daa",
      "name": "Wait",
      "type": "n8n-nodes-base.wait",
      "typeVersion": 1,
      "position": [
        1560,
        460
      ],
      "webhookId": "7771d4be-0ac9-46df-8342-b3cb32ff8fac"
    }
  ],
  "connections": {
    "Execute Workflow Trigger": {
      "main": [
        [
          {
            "node": "Wait",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Wait": {
      "main": [
        [
          {
            "node": "n8n1",
            "type": "main",
            "index": 0
          }
        ]
[details="Summary"]
This text will be hidden
[/details]

      ]
    }
  }
}

Share the output returned by the last node

Information on your n8n setup

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

Hi @Fernando_Arata, I am sorry you’re having trouble.

The way n8n manages the status of an execution has changed a lot recently, which has caused some executions to show up with a wrong status. So the executions from your screenshot could have failed or were cancelled, but n8n would still show them as running.

Unfortunately, the fixes we have released will only prevent these problems going forward, but not address old execution data.

So my suggestion here would be to manually remove these older executions from the database, then upgrade to the latest available n8n version including all bug fixes.

To edit an SQLite database you could (for example) use Beekeeper Studio (Community Edition). The database file to open usually lives in your home directory at /home/Fernando_Arata/.n8n/database.sqlite (replace Fernando_Arata with your actual Ubuntu username). The executions can then be found in (and deleted from) the execution_entity table.

1 Like