# Pattern for pausing a Make scenario while a human reviews an AI video draft

**URL:** <https://community.make.com/t/pattern-for-pausing-a-make-scenario-while-a-human-reviews-an-ai-video-draft/112270>\
**Category:** Questions\
**Tags:** data-store, best-practices, ai, webhooks\
**Created:** [July 21, 2026, 7:11am UTC](https://community.make.com/t/pattern-for-pausing-a-make-scenario-while-a-human-reviews-an-ai-video-draft/112270 "2026-07-21T07:11:35Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Samuel11](https://avatars.discourse-cdn.com/v4/letter/s/da6949/32.png) [@Samuel11](https://community.make.com/u/Samuel11)\
**Post date:** [July 21, 2026, 1:11pm UTC](https://community.make.com/t/pattern-for-pausing-a-make-scenario-while-a-human-reviews-an-ai-video-draft/112270/4 "2026-07-21T13:11:40Z")

</div>

To build a highly robust, enterprise-grade human-in-the-loop workflow, you should avoid attempting to “pause” or delay a single scenario run (which will hit execution timeouts and waste operations).

The optimal architectural pattern is to split this into two asynchronous scenarios connected by a database (such as Airtable or a Make Data Store) and a Webhook.

Here is how you structure this pattern:

* * *

### Scenario 1: Intake, Hold & Notify (The “Pause”)

This scenario handles the initial request and halts the automated flow until a human acts.

1. Trigger: New Form Submission (Form / request enters).
2. Action: Create Record (Airtable / Make Data Store)
  - Store all request details.
  - Set a field called “Status” to: Pending Review.

3. Action: Generate Review Action Link
  - If using Airtable, you can use an Airtable Interface with an “Approve” button that triggers a webhook.
  - Alternatively, generate a custom webhook URL that includes the Record ID as a parameter (e.g., [https://hook.make.com/your-webhook-id?recordId={{Airtable\_Record\_ID}](https://hook.make.com/your-webhook-id?recordId=%7B%7BAirtable_Record_ID%7D)}).

4. Action: Send Notification (Slack / Email)
  - Notify the designer with the request details and the active Review Link.

At this point, Scenario 1 terminates. No operations are wasted, and there are no timeout risks.

* * *

### Scenario 2: Action & Release (The “Resume”)

This scenario triggers only when the human designer explicitly approves the draft.

1. Trigger: Custom Webhook (Instant)
  - Triggers when the designer clicks “Approve” in your review tool or updates the status in Airtable, passing the original Record ID.

2. Action: Get Record (Airtable / Make Data Store)
  - Fetch the original request details using the Record ID passed from the webhook.

3. Action: Continue Workflow
  - Resume the automation (e.g., trigger the final AI video rendering, notify the client, update the database status to “Approved”).

* * *

### Why this pattern is optimal:

- Zero Timeout Risk: The human reviewer can take 10 minutes or 10 days; the system will never time out.
- Operation Cost: No operations are consumed while the system is “waiting.”
- Reliable State Machine: You maintain a permanent audit trail of your creative requests and their current statuses in your database.

---

_[View the full topic](https://community.make.com/t/pattern-for-pausing-a-make-scenario-while-a-human-reviews-an-ai-video-draft/112270)._