N8n Status Update Problem At Queu Mode

Questions
1

Describe the problem/error/question

We are using n8n at queue mode. At our business logic we have some data and we process it with “Loop Over Items”. In every loop we call somewhere with our custom node. Our custom node works same as “Wait” node.

At loop branch we send data to our custom node and we put execution to wait at our custom node. When data processed at somewhere else in our system, it calls back waited workflow with webhook and it continues to process other datas until it finishes.

But when we process data too fast sometimes n8n couldn’t put execution to wait fast enough. When we call webhook back it returns “Conflict” http status and it says “execution is already running.” Because it didn’t update workflow status to waiting. When we look the logs we saw that n8n updates workflow status async.

Can we change this async status updating mechanism to synchronous? What can we do to avoid this problem?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • **n8n version: 1.59.3
  • **Database (default: SQLite): PostgreSql
  • **Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
1 Like
2

hello @Mustafa_fimple

Maybe better to set the retry behavior if you receive the Conflict status?

I don’t think it’s possible to change the n8n logic as it uses async methods whenever possible

3

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