> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/admin-api-reference/admin-scenarios.md).

# Admin / Scenarios

## Reactivate 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.<br>

```json
{"openapi":"3.0.0","info":{"title":"Web API v2 - Public ","version":"1.0.0"},"tags":[],"servers":[{"url":"https://eu1.make.com/api/v2","description":"EU1 production zone"},{"url":"https://eu2.make.com/api/v2","description":"EU2 production zone"},{"url":"https://us1.make.com/api/v2","description":"US1 production zone"},{"url":"https://us2.make.com/api/v2","description":"US2 production zone"},{"url":"https://eu1.make.celonis.com/api/v2","description":"Celonis EU1 production zone"},{"url":"https://us1.make.celonis.com/api/v2","description":"Celonis US1 production zone"}],"security":[{"token":["admin:write"]}],"components":{"securitySchemes":{"token":{"type":"apiKey","name":"Authorization","in":"header","description":"Authorize the API call with your API token in the `Authorization` header with the value: `Token your-api-token`.\n\nIf you don't have an API token yet, please refer to the [\"Authentication\" section](/api-documentation/authentication) to learn how to create one.\n"}}},"paths":{"/admin/scenarios/reactivate":{"post":{"tags":["Admin / Scenarios"],"summary":"Reactivate scenarios","description":"Reactivates up to 10,000 scenario IDs in the current zone, or 20 with `reanalyze: true` (before deduplication). Duplicate IDs are processed once.\nRequires the `scenarios get` admin permission. Deleted, locked and executing scenarios are skipped.\n\nWith `reanalyze: true`, also requires the `scenario edit` admin permission. Rebuilds derived\nbindings from the stored published blueprint and draft before activation. Existing resources can\nbe relinked; deleted resources, invalid connection credentials and gone webhooks cannot be repaired.\nUse reanalysis only to repair missing bindings, for example after restoring an accidentally deleted scenario.\nScenarios are processed sequentially within each request, each in its own atomic transaction.\nEach reanalysis database statement is limited to 5 seconds, with at most 1 second waiting for a lock.\nTimeouts roll back that scenario and return a failed result; subsequent IDs are still processed.\nResults retain input order after deduplication. A failure rolls back that scenario and does not stop other IDs.\nDeleted teams and organizations are skipped. A scenario without a published blueprint cannot be activated.\nStored blueprint JSON and versions are preserved; the draft is never published.\n\nAlready active scenarios are reanalyzed but their scheduling is reset only with `forceIfActive: true`.\n`reanalysis` describes the analysis phase separately from the existing activation `status`.\nMerely reanalyzing an active scenario does not increment `summary.reactivated`.\n\nWith both `dryRun` and `reanalyze`, performs the real database operation and rolls its transaction back,\nincluding derived bindings, runtime state, scheduling and scenario events.\nIt has the same database cost and locking impact as execution and the same 20-ID limit. Request auditing still applies.\nDry-run results describe the state at the time of the check and do not guarantee a later execution succeeds.\nWithout `reanalyze`, the existing reactivation and dry-run behavior is unchanged.\n","requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","required":["scenarioIds"],"oneOf":[{"properties":{"reanalyze":{"enum":[false]}}},{"required":["reanalyze"],"properties":{"reanalyze":{"enum":[true]},"scenarioIds":{"maxItems":20}}}],"properties":{"scenarioIds":{"type":"array","minItems":1,"maxItems":10000,"description":"Scenario IDs in the current zone. Duplicates are removed before processing. With reanalyze enabled, at most 20 IDs may be submitted (before deduplication), including dry runs.","items":{"type":"integer","format":"int32","minimum":1,"maximum":2147483647}},"dryRun":{"type":"boolean","default":false,"description":"Return predicted results. With reanalyze, perform the real operation in a transaction and roll it back; this has the same database cost and the same 20-ID limit as execution."},"forceIfActive":{"type":"boolean","default":false,"description":"Reset state and scheduling even for already active scenarios."},"reanalyze":{"type":"boolean","default":false,"description":"Rebuild bindings to existing resources before reactivation; also analyze already active scenarios."}}}}}},"responses":{"200":{"description":"Individual results and counts grouped by activation status. Per-scenario failures also use HTTP 200.","content":{"application/json":{"schema":{"type":"object","required":["results","summary"],"properties":{"results":{"type":"array","items":{"type":"object","required":["scenarioId","status","message","prevIslinked","prevIsinvalid","prevInvalidationReason","prevErrorOccurCount"],"properties":{"scenarioId":{"type":"integer"},"status":{"type":"string","enum":["reactivated","would_reactivate","already_active","deleted","executing","locked","not_found","failed"]},"message":{"type":"string","nullable":true,"description":"Reason for the activation result or a safe description of a reanalysis error."},"reanalysis":{"type":"string","enum":["succeeded","would_succeed","failed","skipped"],"description":"Present only when reanalyze is true. Failed analysis leaves the scenario unchanged."},"prevIslinked":{"type":"boolean","nullable":true},"prevIsinvalid":{"type":"boolean","nullable":true},"prevInvalidationReason":{"type":"string","nullable":true},"prevErrorOccurCount":{"type":"integer","nullable":true}}}},"summary":{"type":"object","required":["total"],"description":"Total unique IDs plus a count for each activation status present in results.","properties":{"total":{"type":"integer"}},"additionalProperties":{"type":"integer"}}}}}}},"400":{"description":"Invalid scenario IDs, more than 20 submitted IDs with reanalyze enabled (including dry runs), more than 10,000 IDs otherwise, or non-boolean options."},"401":{"description":"Authentication is required."},"403":{"description":"The caller is not an administrator or lacks a required admin permission."}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.make.com/white-label-documentation/admin-api-reference/admin-scenarios.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
