Thora Cloud
A direct line to Thora

Start a conversation

What can we help make simpler?

Tell us what you need. A real person will point you to the right place.

Email Thorahello@thora.cloudExplore SupportSee the available support paths
Browse docs Review changes

Help and guides

Review changes

Find the pending decision and approve only the change you intend to make.

Before you start

You need the role required for the decision. Check the organization, resource, destination, and any cost before approving.

Steps

  1. For purchases, open the organization purchase area and choose Review purchase requests.
  2. For a site release, open the site and use Review live release when available.
  3. For DNS, review the proposed action in the domain DNS view. For Compute, check Needs attention.
  4. Read the exact proposed change before approving or rejecting it.
  5. Return to the resource to check whether the approved work completed.

What to expect

The decision is recorded for the reviewed change. Approval does not guarantee that deployment or provider work has finished.

If something goes wrong

If the change or destination has changed since you reviewed it, read the new proposal. Do not repeatedly submit an uncertain operation or approve a different change just to clear a warning.

Technical reference

Separate intent, decision, and execution

  1. A customer or agent reads current state and submits one exact proposal.
  2. Thora records the requester, target, operation, expected state, version or revision, expiry, and digest.
  3. For approval-gated actions, a signed-in direct organization administrator reviews the exact proposal in the header notifications menu.
  4. The decision path revalidates membership, capability, target state, and proposal digest.
  5. Execution claims one durable receipt before the provider call.
  6. The customer reads the receipt and resulting resource state.

Do not collapse the boundary

  • A developer token cannot call the browser decision route.
  • A write scope does not contain approval authority. An organization-admin DNS write credential can execute record changes on an already hosted zone directly.
  • An agent's statement that the user approved is not a dashboard decision.
  • An approval for one digest cannot approve a newer build, changed record, different resource, or expired proposal.
  • Operator execution cannot be reclassified as customer acceptance.

Handle uncertain outcomes

When a provider may have accepted work but Thora lacks a definitive result, the operation is fenced as uncertain. Do not create a replacement request to make the interface look complete.

  1. Stop automated follow-on work.
  2. Read the proposal, receipt, and resource again.
  3. Reuse the original idempotency key only if the documented endpoint permits a retry.
  4. Escalate to reconciliation when the response says operator review or recovery is required.
  5. Resume only after the control plane records a reconciled state.