You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Believe I found an expected bug and edge-case which I was able to reproduce on both docker and cloud environments so thought it worth reporting.
The following workflow is a simple test which uses
"http" node to fetch an image
"extract to json" node to convert image to base64 string
sends the image data to an API endpoint using the "http" node again
"code" node to perform calculations on the returned data
When testing the workflow specifically on the "code" node step, the "test step" button executes the code without issue.
However, using the "test workflow" button, the code node timeouts with the following output in the docker logs - (I'm able to report on the cloud environment logs)
2024-12-15 10:17:36 Registered runner "JS Task Runner" (UaR7o06g6XEuPWtygrRob)
2024-12-15 10:26:52 Converting circular structure to JSON
2024-12-15 10:26:52 --> starting at object with constructor 'TLSSocket'
2024-12-15 10:26:52 | property '_httpMessage' -> object with constructor 'ClientRequest'
2024-12-15 10:26:52 --- property 'socket' closes the circle
2024-12-15 10:26:52 TypeError: Converting circular structure to JSON
2024-12-15 10:26:52 --> starting at object with constructor 'TLSSocket'
2024-12-15 10:26:52 | property '_httpMessage' -> object with constructor 'ClientRequest'
2024-12-15 10:26:52 --- property 'socket' closes the circle
2024-12-15 10:26:52 at JSON.stringify (<anonymous>)
2024-12-15 10:26:52 at TaskRunnerWsServer.sendMessage (/usr/local/lib/node_modules/n8n/dist/runners/runner-ws-server.js:67:51)
2024-12-15 10:26:52 at TaskBroker.messageRunner (/usr/local/lib/node_modules/n8n/dist/runners/task-broker.service.js:78:48)
2024-12-15 10:26:52 at TaskBroker.handleRequesterDataResponse (/usr/local/lib/node_modules/n8n/dist/runners/task-broker.service.js:236:20)
2024-12-15 10:26:52 at processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-12-15 10:26:52 at TaskBroker.onRequesterMessage (/usr/local/lib/node_modules/n8n/dist/runners/task-broker.service.js:214:17)
2024-12-15 10:26:52
2024-12-15 10:27:52 Task runner timed out during task, restarting...
Workarounds
This timeout bug only seems to happen when using the "test workflow" action in non-production mode. I can confirm the following methods of running the workflow do not experience the timeout.
✅ Running via webhook
✅ Runing via subworkflow
✅ Removing the http nodes from the workflow also seems to work
Bug Description
Believe I found an expected bug and edge-case which I was able to reproduce on both docker and cloud environments so thought it worth reporting.
The following workflow is a simple test which uses
When testing the workflow specifically on the "code" node step, the "test step" button executes the code without issue.
However, using the "test workflow" button, the code node timeouts with the following output in the docker logs - (I'm able to report on the cloud environment logs)
Workarounds
This timeout bug only seems to happen when using the "test workflow" action in non-production mode. I can confirm the following methods of running the workflow do not experience the timeout.
✅ Running via webhook
✅ Runing via subworkflow
✅ Removing the http nodes from the workflow also seems to work
Template.json
To Reproduce
Expected behavior
The execution should not timeout.
Operating System
MacOS & n8n Cloud
n8n Version
1.72.1
Node.js Version
20
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: