Admin / Scenarios
Reactivates up to 10,000 scenario IDs in the current zone, or 20 with reanalyze: true (before deduplication). Duplicate IDs are processed once. Requires the scenarios get admin permission. Deleted, locked and executing scenarios are skipped.
With reanalyze: true, also requires the scenario edit admin permission. Rebuilds derived bindings from the stored published blueprint and draft before activation. Existing resources can be relinked; deleted resources, invalid connection credentials and gone webhooks cannot be repaired. Use reanalysis only to repair missing bindings, for example after restoring an accidentally deleted scenario. Scenarios are processed sequentially within each request, each in its own atomic transaction. Each reanalysis database statement is limited to 5 seconds, with at most 1 second waiting for a lock. Timeouts roll back that scenario and return a failed result; subsequent IDs are still processed. Results retain input order after deduplication. A failure rolls back that scenario and does not stop other IDs. Deleted teams and organizations are skipped. A scenario without a published blueprint cannot be activated. Stored blueprint JSON and versions are preserved; the draft is never published.
Already active scenarios are reanalyzed but their scheduling is reset only with forceIfActive: true. reanalysis describes the analysis phase separately from the existing activation status. Merely reanalyzing an active scenario does not increment summary.reactivated.
With both dryRun and reanalyze, performs the real database operation and rolls its transaction back, including derived bindings, runtime state, scheduling and scenario events. It has the same database cost and locking impact as execution and the same 20-ID limit. Request auditing still applies. Dry-run results describe the state at the time of the check and do not guarantee a later execution succeeds. Without reanalyze, the existing reactivation and dry-run behavior is unchanged.
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
Individual results and counts grouped by activation status. Per-scenario failures also use HTTP 200.
Invalid scenario IDs, more than 20 submitted IDs with reanalyze enabled (including dry runs), more than 10,000 IDs otherwise, or non-boolean options.
Authentication is required.
The caller is not an administrator or lacks a required admin permission.
POST /api/v2/admin/scenarios/reactivate HTTP/1.1
Host: eu1.make.com
Authorization: Token your-api-token
Content-Type: application/json
Accept: */*
Content-Length: 42
{
"scenarioIds": [
123,
456
],
"reanalyze": true
}{
"results": [
{
"scenarioId": 123,
"status": "reactivated",
"message": "Scenario reactivated successfully",
"reanalysis": "succeeded",
"prevIslinked": false,
"prevIsinvalid": true,
"prevInvalidationReason": "Restored scenario",
"prevErrorOccurCount": 3
},
{
"scenarioId": 456,
"status": "already_active",
"message": "Scenario is already active",
"reanalysis": "succeeded",
"prevIslinked": true,
"prevIsinvalid": false,
"prevInvalidationReason": "",
"prevErrorOccurCount": 0
}
],
"summary": {
"total": 2,
"reactivated": 1,
"already_active": 1
}
}Last updated

