Skip to content
txcasttxcasttxcast docs

Refresh, cancel, and share a run

Refresh a source

Section titled “Refresh a source”

After a successful evm.snapshot or http.snapshot, a seated member may request Refresh. A scoped agent can call refresh_source.

Refresh appends an immutable observation and updates the dashboard selection after success. It never changes the effect’s consumed result, program history, run status, notifications, or downstream execution. A failed refresh preserves the prior selection.

Event waits and transaction receipts follow their own durable executor and reconciliation paths; source refresh is not a generic “sync everything” action.

Cancel

Section titled “Cancel”

The run starter or a scoped agent may cancel with exact run-version CAS. Review submitted hashes, Safe proposals, signatures, and active wallet claims first.

Cancellation:

  • prevents new logical work;
  • asks the backend instance to stop;
  • preserves immutable effects, attempts, observations, and audit history;
  • keeps escaped transaction fences until authoritative reconciliation.

It does not reverse onchain or provider activity.

Section titled “Public link”

A public link is tokenized, unauthenticated, read-only access to the sanitized run view. Creating a new link rotates the old token. Revocation removes access without changing execution state.

Review the run for organisation-sensitive public input/output fields before sharing. Internal backend authority, signal keys, resolved capability internals, signatures, and private processing data are never exposed.