Frame.io sending duplicate folder.updated webhooks causing duplicate processing

Automations
, ,
1

Frame is sending duplicate webhook events for the same folder creation, causing my automation to run twice and create duplicate records.

Problem:

  • Create a new folder in Frame

  • Frame sends 2 identical folder.updated webhook events within milliseconds

  • Both events have same folder ID, name, and timestamp

  • This causes duplicate processing in my automation workflow

Webhook details:

  • Event type: folder.updated

  • Both webhooks contain identical payload data

  • Timestamps differ by ~30-70ms

  • This happens 100% of the time when creating folders

Expected behavior:

  • Frame should send only 1 folder.updated webhook per folder creation

  • OR provide a way to identify/filter duplicate events

Current workaround needed:

  • Implement complex deduplication logic in receiving system

  • This shouldn’t be necessary for webhook consumers

Is this expected behavior? If so, how should we handle duplicate events on the receiving end?

2

I’ve had the same for comment webhooks. It’s not all the time, b it every few times it’ll send a double webhook.

3

Hi @ebrown ! I am also seeing two events come through when I create a folder and immediately name it. If I create the folder and leave it, I don’t get a webhook. If I then rename it later, I get a single webhook for the rename. It’s possible the create + immediately rename is looking at it as two events. I’ll bring this behavior back to the team.

For your workflow, would it make more sense to catch folder.created?