n8n Community

Describe the problem/error/question Hi people, we want to automatically deactivate inactive users from n8n. Is there a way to do so or to retrieve the last login date of a user? I looked at the users api but this data seems not returned. Thank you! What is the error message (if any)? Please share your workflow (Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.) Share the output returned by the last node Information on your n8n setup n8n version: 2.31.7 Database (default: SQLite): PosgreSQL n8n EXECUTIONS_PROCESS setting (default: own, main): queue Running n8n via (Docker, npm, n8n cloud, desktop app): Docker Operating system: Linux 1 post - 1 participant Read full topic

Describe the problem/error/question Hi people, we want to automatically deactivate inactive users from n8n. Is there a way to do so or to retrieve the last login date of a user? I looked at the users api but this data seems not returned. Thank you! What is the error message (if any)? Please share your workflow (Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.) Share the output returned by the last node Information on your n8n setup n8n version: 2.31.7 Database (default: SQLite): PosgreSQL n8n EXECUTIONS_PROCESS setting (default: own, main): queue Running n8n via (Docker, npm, n8n cloud, desktop app): Docker Operating system: Linux

(topic deleted by author) 1 post - 1 participant Read full topic

(topic deleted by author)

Кто-нибудь может подсказать, как создать авито помощника? 1 post - 1 participant Read full topic

Кто-нибудь может подсказать, как создать авито помощника?

The error means the webhook path is already registered by another active workflow: course/n8n102/new-order Normally the fix is to deactivate the other workflow or change the webhook path In your case the link opens a workflow you do not have permission to access. So it may be an old or shared Academy workflow or a workflow in another project. I would first search your workflows-projects for another Webhook node using the same path. If you can’t find or access it this may need an n8n Academy-admin cleanup because the path is still registered to a workflow you cannot manage.

The cause and the concurrency fix above are spot on, so I will just add the part questions 3 and 4 were really after: how to find the culprit, and how to stop an intermittent trip from quietly costing you a run. To pinpoint it, set N8N_LOG_LEVEL=debug so the failing node and execution id show up in the logs, and point every critical workflow at one central Error Trigger workflow that records the execution id, the workflow name and the last node into a sheet or table. Because this fires intermittently across many unrelated workflows, a few days of that log turns “random everywhere” into a ranked list of which workflows and nodes actually trip it, which is usually a handful of heavy IF, Filter or Set expressions running over large item sets. On not losing work: the timeout throws, so it is at least a loud error rather than a silent wrong output, which is good. But an intermittent hard error still drops that run unless you catch it. Since you noticed a retry usually passes, have the Error Trigger path retry the execution once and only alert you if the retry also fails. That way the flaky ones self heal and you only get pinged when something is genuinely stuck, instead of a run quietly vanishing. And if the workflow writes rows downstream, a simple daily count against an expected floor tells you on the rare occasion a trip actually cost you data rather than just a retry.

HI All Another quick request for any update? Thanks