# Duplicate Facebook posts occurring despite single execution in History and time-buffer filters

**URL:** <https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364>\
**Category:** Questions\
**Tags:** error, meta-facebook, airtable\
**Created:** [May 4, 2026, 2:07pm UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364 "2026-05-04T14:07:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marcela\_Araujo](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Marcela\_Araujo](https://community.make.com/u/Marcela_Araujo)\
**Post date:** [May 4, 2026, 2:07pm UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364/1 "2026-05-04T14:07:37Z")

</div>

### 🎯 What is your goal?

I need to prevent duplicate posts on Facebook. My scenario is triggered by an Airtable search every hour (or when scheduled). Even with a filter to only pick records where the scheduled time is in the past, some posts are being published twice, even though the Make history shows only one successful execution per hour.

### 🤔 What is the problem & what have you tried?

The problem is double-posting on Facebook.

What I’ve already tried:

Time-buffer formula: I’m using an Airtable formula to only fetch records where {Scheduled Time} \<= DATEADD(NOW(), -2, ‘minutes’) to avoid race conditions.

Sequential Processing: I tried enabling it, but switched back to “No” to avoid scenario blocking, as I’m handling dozens of pages.

Error Handling: I have Error Handlers (blue dotted lines) with “Commit” modules to ensure failed runs don’t stay incomplete.

History check: The Make history shows only ONE successful run at the time of the duplicate posts.

I suspect there might be a delay between Airtable updating the status and the next run, or some Facebook API ghost-retrying.

### 📋 Error messages or input/output bundles

No error messages in the history logs. The logs show “Success” with 1 bundle processed, but 2 posts appear on the Facebook Page at the exact same time.

### 📸 Screenshots (scenario flow, module settings, errors)

 ![Captura de tela 2026-05-04 110151.png](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/5/2/525440da0198f9460703a8d949842cdfacc2cbeb.jpeg)

---

<div class="post-metadata">

**Author:** ![mszymkowiak](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mszymkowiak/32/41436_2.png) [@mszymkowiak](https://community.make.com/u/mszymkowiak)\
**Post date:** [May 6, 2026, 12:42am UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364/3 "2026-05-06T00:42:24Z")

</div>

Hello,

That’s an interesting one.

Your scenario log clearly shows only one post was created.  
Are you sure there isn’t a second scenario or an Airtable Webhook that could be triggering a duplicate?

The most common cause would be `Search records` returning more than one bundle – each bundle would then create a separate post. But your screenshot and operations log show only 3 credits used, so that’s not the case here.

If you have the [Make DevTool](https://help.make.com/make-devtool) extension installed, it might give you more debug info.

Have a nice day,  
Michal

---

<div class="post-metadata">

**Author:** ![samliew](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/samliew/32/13327_2.png) [@samliew](https://community.make.com/u/samliew)\
**Post date:** [May 7, 2026, 1:50am UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364/4 "2026-05-07T01:50:21Z")

</div>

> [@Marcela\_Araujo](#):
>
> Time-buffer formula: I’m using an Airtable formula to only fetch records where {Scheduled Time} \<= DATEADD(NOW(), -2, ‘minutes’) to avoid race conditions.

We’d love to help, however, we require more information that demonstrates the problem to help us reproduce the scenario and any issues and errors. To allow others to assist you, please provide the following:

## A. All Relevant Screenshots

We need to see what you’re working with to give you the best advice. Screenshots are important because Make is a visual editor — a picture provides us with more context.

It would help us identify the issue by having screenshots of:

- relevant **module fields** (_showing how you’ve used any built-in functions, and how you’ve mapped the variables_),
- relevant filters between modules (_showing which operators and any built-in functions you’ve used, and how you’ve mapped the variables_),
- relevant module input/output bubbles,
- if applicable, any error messages,
- and if applicable, any external services (_spreadsheet headers/ sample data/ regex101.com/ etc. to show the item/ record exists, and is set up correctly_).

> **Expand Instructions ◀**
>
> > Please directly upload screenshots into the post editor. Using the forum’s image hosting allows for zooming in when clicked, and avoids third-party cookies or tracking.
> > 
> > ## Taking Screenshots
> > 
> > - **Microsoft Windows:** Take screenshots using the “[Windows Snipping Tool](https://support.microsoft.com/en-au/windows/use-snipping-tool-to-capture-screenshots-00246869-1843-655f-f220-97299b865f6b)”, by pressing either PrtSc _or_ WinShiftS keys on your keyboard.
> > - **MacOS:** Take screenshots by pressing CommandShift4 keys on your keyboard.
> > 
> > ## Uploading Images
> > 
> > - **Drag** image files directly into the rich-text editor, or
> > - **Click** on the upload button in the editor toolbar to select files:  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/5/c/5c7c8f11d1316a1cc6984d252a732946207bf634.png)

## B. Scenario Blueprint

Providing your scenario will allow others to quickly recreate and see how you have set up the mappings in each module, and also allows us take screenshots or provide module exports of any solutions we have for you in return. This would benefit you in implementing our suggestions as you can view screenshots of the changes or paste corrected modules back into your scenario.

> **Expand Instructions ◀**
>
> > ## A. Export Blueprint
> > 
> > In the scenario editor, click the three dots at the top-right, then select “ **Export blueprint** ”.  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/1/5/152b265128a71a7a2937c4f701c4beba3f5f610c.png)
> > 
> > - You can upload files and images to this forum by clicking on the upload button:  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/5/c/5c7c8f11d1316a1cc6984d252a732946207bf634.png)
> > 
> > ## B. Create Public Share Link
> > 
> > In the scenario editor, click on the **Share button** :  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/0/a/0ad95b052c1a1651a310868e4eacd432c289022c.png)  
> > Read more about the [scenario sharing feature](https://help.make.com/scenario-sharing) in the Help Centre.

## C. _Properly-formatted_ Output Bundles from a Scenario Run

Please provide the **Output bundle** of each of the relevant modules from the [Scenario History](https://help.make.com/scenario-history), or by [re-running the scenario](https://help.make.com/scenario-run-replay).

> **Expand Instructions ◀**
>
> > Click on the white speech bubbles on the top-right of each module and select “**Download output (_or input_) bundles**”.  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/2/8/2876156ab3ea5bc9e40bbc0edfb9f025406b7c48.png)
> > 
> > ## A. Upload a Text File
> > 
> > Save each bundle contents in a **plain text** editor as a `moduleNumber-output.txt` file. Open the file to check if it has not added additional formatting or encoded the plain text.
> > 
> > - You can upload files and images to this forum by clicking on the upload button:  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/5/c/5c7c8f11d1316a1cc6984d252a732946207bf634.png)
> > 
> > ## B. Insert a Formatted Code Block
> > 
> > If you are unable to upload files on this forum, alternatively you can **paste the bundles** AND **format them correctly** with the “Preformatted Text” (code) button in the rich-text editor. Otherwise the forum software will change the content, making them invalid!
> 
> > # ⚠Formatting IS Important! ⚠
> > 
> > Here are some ways to provide text content in a way that it won’t be modified by the forum.
> > 
> > - **Method 1: Type code fence manually** —  
> > Manually type three backticks ````` in a separate line before and after the content, like this,
> > 
> > - **Method 2: Highlight the pasted content, then click the preformatted text/code button** —  
> > ![](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/7/b/7b91db14846cb99e1084b77e4362a273f8324e74.png)
> > 
> > - **Method 3: Upload your file elsewhere and share the public link** —  
> > This method is only advised for large files exceeding the forum upload limit.

Providing the Output bundle will allow others to replicate what is going on, especially if there are complex data structures (like nested arrays and collections) and data from external services. This helps us with answering your question with valid examples, like mapping raw variable names (instead of the label/display name).

* * *

Sharing these details will make it easier for others to assist you, so that you can get better answers, faster.

— @samliew

---

<div class="post-metadata">

**Author:** ![Marcela\_Araujo](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Marcela\_Araujo](https://community.make.com/u/Marcela_Araujo)\
**Post date:** [May 22, 2026, 9:31pm UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364/5 "2026-05-22T21:31:20Z")

</div>

Hi @samliew,

Thank you for looking into this!

I have already uploaded **all relevant screenshots (A)** and attached my **Scenario Blueprint (B)** to this post. However, I am a bit confused about how to extract or properly format the **Output Bundles (C)** from my history log, so I am missing that part.

Looking closely at the execution history of the exact moment the bug occurred (which started at 22:15:11), the total scenario duration was **1 minute** , and the `Facebook Pages` module took **66.3 seconds** to respond.

Despite this extreme slowness from Meta’s side, the module completed successfully with a green bubble (returning only one post ID), and the scenario immediately updated the Airtable record status to “Published”.

Because the Facebook module took more than 60 seconds to process, it pushed the final execution into the 22:16 minute mark. Since Make only executed one single cycle, generated one bundle, and closed the run successfully, I strongly believe this duplication is an internal server-side glitch on Facebook’s end (like a replication delay or internal retry within their API when handling the binary upload) rather than a Make scenario logic error.

Given these metrics (1-minute run / 66s Facebook delay), do you think this is a known Meta API glitch? Any insights based on the Blueprint and screenshots would be greatly appreciated!

 ![Captura de tela 2026-05-20 231753](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/c/d/cd8c00d1b61f45f305bbc9b33c5ea4d86815180b.jpeg)

 ![Captura de tela 2026-05-20 231806](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/b/6/b60cb9f9f808832e1d23135186f2f4d4cbdbac27.png)

 ![Captura de tela 2026-05-20 231800](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/9/3/93aa1e14a43f36e2723294dcd365e7222ca05cd7.png)

 ![Captura de tela 2026-05-22 182408](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/3/c/3c893f6f39548ce975e06fe714eca0df805544dc.png)

[Publicação de Estáticos de Boxoffice USA.blueprint.json](https://community.make.com/uploads/short-url/1trKWcztQJwhpy2wsa1ifjRK1nG.json) (107.5 KB)

[scenario-4341149-logs.csv](https://community.make.com/uploads/short-url/itDIs0rfkWXFo4mS3pEB2pGOMd0.csv) (69.1 KB)

---

<div class="post-metadata">

**Author:** ![Marcela\_Araujo](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Marcela\_Araujo](https://community.make.com/u/Marcela_Araujo)\
**Post date:** [May 22, 2026, 9:33pm UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364/6 "2026-05-22T21:33:09Z")

</div>

> [@mszymkowiak](#):
>
> Hello,
> 
> That’s an interesting one.
> 
> Your scenario log clearly shows only one post was created.  
> Are you sure there isn’t a second scenario or an Airtable Webhook that could be triggering a duplicate?
> 
> The most common cause would be `Search records` returning more than one bundle – each bundle would then create a separate post. But your screenshot and operations log show only 3 credits used, so that’s not the case here.
> 
> If you have the [Make DevTool](https://help.make.com/make-devtool) extension installed, it might give you more debug info.
> 
> Have a nice day,  
> Michal

Hi @Michal,

Thank you for your insights!

To answer your questions: No, I absolutely do not have any other duplicate scenarios running for this same page, nor do I use any Airtable Webhooks that could trigger a second post. This is the one and only workflow handling this specific automation.

As you correctly pointed out from the logs, only 3 credits were used, meaning Make only initiated and processed one single operation cycle during that run.

I also tried using the **Make DevTool extension** to capture more debug information as you suggested, but it didn’t show anything out of the ordinary—it just confirmed a single POST request being sent to Meta and a single successful post ID coming back.

Given that the `Facebook Pages` module took an unusual **66.3 seconds** to respond (as seen in my execution history), it seems the request got delayed heavily on Meta’s side, which pushed the completion into the next minute mark. This extreme delay makes me believe that Facebook’s internal servers processed the same payload twice due to a timeout/caching echo on their end, completely independent of Make or Airtable.

Since Make did its job perfectly in a single execution, do you think there’s any parameter we can tweak to prevent Meta from duplicating requests when their API is lagging?

Have a great day!

---

<div class="post-metadata">

**Author:** ![samliew](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/samliew/32/13327_2.png) [@samliew](https://community.make.com/u/samliew)\
**Post date:** [May 24, 2026, 10:00am UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364/7 "2026-05-24T10:00:25Z")

</div>

Scenario logs are not good enough - they don’t really provide useful information like how the Airtable modules are set up, or what data does the airtable modules output during different scenario executions.

---

<div class="post-metadata">

**Author:** ![Marcela\_Araujo](https://avatars.discourse-cdn.com/v4/letter/m/d6d6ee/32.png) [@Marcela\_Araujo](https://community.make.com/u/Marcela_Araujo)\
**Post date:** [May 24, 2026, 9:59pm UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364/8 "2026-05-24T21:59:54Z")

</div>

Hi @samliew,

To clear any doubts about what my Airtable module is outputting during execution, I am attaching a **new screenshot** (`Captura de tela 2026-05-24 185808.png`) showing the raw data inside the **OUTPUT** section of the `Search Records` module from that exact run.

As you can see, the module found and outputted **exactly ONE single bundle** (`Bundle 1`). My settings are locked to `Limit = 1` and `Sequential Processing = NO`.

Since Airtable only passed a single record to the rest of the workflow, and the entire scenario executed only once, it is physically impossible for the duplicator to be caused by multiple bundles coming out of Airtable.

Since I already provided the **Scenario Blueprint (.json)** in my original post, you can verify that my configuration is bulletproof, including the negative time-buffer formula that prevents subsequent runs from picking up the same record.

Everything points back to the **66.3-second response delay** from the Meta API module. It seems Facebook’s servers processed the exact same binary payload twice due to their own latency glitch, entirely independent of Make’s execution or Airtable’s outputs.

Given this definitive evidence that Airtable only generated one bundle, what else could be causing the Meta API to replicate this post?

---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [August 22, 2026, 10:03pm UTC](https://community.make.com/t/duplicate-facebook-posts-occurring-despite-single-execution-in-history-and-time-buffer-filters/108364/9 "2026-08-22T22:03:11Z")

</div>