Pause, hand over or cancel Make: scenarios, connections and billing

Define the purpose and intake route

Decide whether this is maintenance, an operator change or retirement. Record the stop time, expected restart, temporary intake route and person responsible for unfinished work. If a public form keeps accepting requests while its downstream process is stopped, those requests still need an owner. Include source-side communication and processing in the transition plan.

Separate scenario status from contract status

Review the scenario’s active state and scheduling, then inspect running executions, queued work and incomplete executions separately. Do not assume a pause cancels every effect already in progress. Conversely, stopping a scenario does not cancel a paid subscription. Put both operational and billing decisions on the checklist when the intention is to end the service.

Prepare a useful handover inventory

List scenario ID, purpose, source, storage destination, recipients, connection names, operator, incident contact and billing owner. Add the last completed ID and known unfinished IDs. Keep passwords and API keys in the organization’s credential-management process rather than the inventory. State the actions a successor must be able to perform, not only which screens they should be able to open.

Transfer organization access and external access

The organization Owner can transfer ownership to an existing member. First confirm that the successor can reach the organization and required teams. Organization ownership does not transfer a person’s Google or Slack account. Before an employee loses access, arrange appropriate business connections and check the operations that depend on them. Treat external permissions as a distinct handover task.

Preserve configuration separately from operational data

Use Export blueprint in the Scenario Builder menu to save configuration. Blueprints include modules, settings and mappings; an importer still configures their own connections. Preserve ledger data, processed keys and unfinished IDs separately. Import into an isolated scenario and check destinations before describing the collection as a recoverable backup. A file that merely downloads is not evidence of successful restoration.

Cancel the intended organization’s subscription

An Owner or Admin can open Org > My Plan > Subscription and choose Cancel subscription under Manage. Follow the current prompts for lost features, retained teams and the target organization. Preserve the confirmation email and end date. The current billing period normally remains usable; the later state also depends on conditions such as other Free organizations owned by the account.

Distinguish Free transition, pause and deletion

Unused credits do not simply carry into the Free allowance after cancellation. Check the current restrictions for several organizations and the possibility of an unlicensed organization. If the goal is temporary inactivity, review Pause subscription and its effect on scenarios. Deleting an organization is irreversible; it is a separate action and is not required merely to cancel a subscription.

Close with both intake and billing reconciliation

Reconcile source records, storage and notifications across the transition time. Confirm that the successor can explain unfinished work and inspect the subscription state and next-charge information. This guide explains a procedure; it has not changed the reader’s subscription or executed an account handover. Keep a dated operational record of the actions actually completed.

• Reauthorize or replace connections safely
• Review unfinished work before recovery
• Review pricing and plan conditions
• Plan service-account handover across tools