I am using the n8n Cloud plan and have encountered the following issue across multiple workflows:
All nodes in the workflow execute smoothly, with the entire workflow completing in under one second.
However, when I add a Code Node (JavaScript), the workflow times out at the Code Node. This occurs regardless of the complexity of the code or the amount of data being processed. Even minimal code (a few lines) and a small number of items trigger the same behavior.
If I replace the Code Node with a Set Node using an equivalent inline expression, the workflow performs as expected, even when processing the same data.
The issue does not occur consistently but happens sporadically, making it seem like a resource or compatibility issue on the server side.
Has anyone experienced similar issues or found a solution? Any ideas on how to address this problem?
Obviously that helped. Since deactivation the error did not occur again. Thanks much!
As I saw in the linked docs, TaskRunners are still in beta. Is there a chance to optout from beta features in a cloud instance as I prioritize reliability and stability over quick access to new features?
We are rolling out TaskRunner feature to all workspaces gradually and fixing any issues along the way. Deactivating TaskRunner for you could be considered as opting out.