The n8n node does not return the executions in the waiting state

[VidSanchez]

Hi!

I am using the n8n node with the Get Many operation with a filter for the Status = Waiting and I think it does not return the executions correctly.

This is the WF:

I’ve found this thread and read the Wait node documentation and for wait times less than 65 seconds, n8n does not save data to the database (I don’t know if this could be the reason). Therefore, for testing purposes, I have created another workflow that launches a 5 minute Wait.

How to get status from nodes using the n8n API?

I’m executing a workflow and in some point the node has the status of waiting: [image] I’m using the API provided by n8n (API reference | n8n Docs) in order to get information about the workflow: https://docs.n8n.io/api/v1/executions/{id} Nevertheless, the information I’m getting points the node status as success: “executionStatus”: “success” this is different from the console where the diagram points the status as waiting, it is possible to get this information using the API provided by n…

Here is the test wf:

The issue is that although I can see wf executions in waiting state in the executions tab, n8n node (I have also tested with an HTTP request to the API with same results) does not return those executions.

Can anyone tell me if the n8n node has a bug?

Thank you in advance!

My n8n setup

• n8nVersion: 1.79.3
• platform: docker (self-hosted)
• nodeJsVersion: 20.18.2
• database: sqlite
• executionMode: regular

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[barn4k]

hello @VidSanchez

yes, seems the get many doesn’t retrieve waiting executions at all

[JeremyEHT]

Is there any update on the status of resolving this or an alternative approach to getting the same information through a code node?

I just discovered this this morning and haven’t poked at the api yet to determine if its a node or api issue.

Referenced api:

API reference | n8n Docs

[VidSanchez]

I just tested it (again) by making an API call and… same result:

{
  "data": [],
  "nextCursor": null
}

Of course, there are workflows in Waiting status…

[barn4k]

AFAIK, there were no changes in the API.

You can utilizu the node Remove Duplicates, which may look into the previous executions and filter out the matching fields from the current execution

[VidSanchez]

My goal is to get workflows with status Wait. Neither with the n8n node nor with its API I have been able to do it.

I have the suspicion that this is a bug.

[barn4k]

you can try submitting a bug report via GitHub. n8n team reacts to them better

[VidSanchez]

@VidSanchez

I am using the n8n node with the Get Many operation with a filter for the Status = Waiting and I think it does not return the executions correctly.

This is the WF:

Done!

n8n Node Fails to Retrieve Executions in 'Waiting' Status