My flow doesn't seem to be honoring my the lock I put on a Google Sheet

Describe the problem/error/question

I have a flow that grabs my Mastodon post and posts it to my Pixelfed account.
I have a working Webhook so the work flow gets triggered when expected.
HOWEVER, for some reason it might get triggered 2x, 3x, 4x in a row posting duplicate posts to my Pixelfed account.

So I have a Google Sheet that I use to track a Lock status.
the flow starts and I update the sheet with LOCKED
The critical flow happens and we pull and post the data.
There’s a 30 sec wait timer after the post, just to give things a chance to settle.
The Flow ends and the sheet gets updated with “Unlocked.”

What is the error message (if any)?

Problem is that even with this ‘lock’ in place, the Workflow can be triggered multiple times.

So I’m asking for ideas on what N8N function I can use to put a lock in place to prevent the retriggering of my workflow.
Currently, I’m still working on logic that stops the work flow IF the retrieved Post ID is already in another Google Sheet. Something isn’t quite right about it.

Please share your workflow

Regarding my flow, I can post it, but I’d need to clean it up so that my credentials aren’t all over the place.

(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: 1.45.1
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Running n8n via docker
  • Operating system: Synology NAS

hello @Rodney_Almodovar

If you placed your credentials into the n8n credentials object, than you don’t need to clear anything, that information won’t be accessible to us. Only if you have something in cleartext somewhere in the nodes, then yes, it should be cleared (you should use credentials always, as they are encrypted).

As for the subject, it’s hard to say what the issue is without the looking into the workflows. Maybe you need a message broker, like RabbitMQ

1 Like

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