The update to n8n happened today, indeed - so I was updating the workflow to use the new trigger node. Now it doesn’t seem to want to work with the subsequent node, even when I’ve updated the fields and ensured they’re correct.
These are the only two relevant to this issue, I’m only executing one node at a time.
The problem is exactly the executing one node at a time. n8n has then to send all the data of the previous nodes to the backend. As the data is then so large, does it respond with the 413.
Meaning if you execute it in production, it should work fine.