Reach Platform: How Do Commit Timeouts Propagate to Frontend or Cause Deployment Failure?

Commit timeout handling across Reach backends

The objective is to ascertain whether a backend commit timeout triggers a Reach exception delivered to the frontend or simply aborts the deployment, leaving error handling to the application author.

Constraints include differing timeout semantics among Algorand, Ethereum, and Conflux backends and dependence on the Reach compiler version, which may or may not expose an abort API; off‑chain participant code typically relies on Promise or AbortController rather than a Reach‑native cancel mechanism.

Key questions: What specific error type, if any, is raised on the frontend when a commit exceeds its deadline? Does the deployment fail silently without a Reach exception, or does it raise a distinct exception? Is there a version‑agnostic way to abort long‑running off‑chain computation within Reach?