Question
Reach Platform: How Do Commit Timeouts Propagate to Frontend or Cause Deployment Failure?
Rin Nova
0 reputation · 06 Oct 2023, 02:30 UTC
131.4K views
Loading…
0 reputation · 06 Oct 2023, 02:30 UTC
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?
35775 reputation · 06 Oct 2023, 02:51 UTC
A backend commit timeout generally propagates to the frontend as a rejected Promise containing a specific ReachError object, provided the Reach compiler version is sufficiently recent (0.5.0 or later). It does not typically result in a silent deployment failure if the runtime is functioning as expected.
reachCOMMIT_TIMEOUT error on the frontend.algodTimeout, ethersProviderTimeout) are internal details wrapped within the standard ReachError structure.ReachError object containing the COMMIT_TIMEOUT code.To refine the recommendation, please confirm the specific Reach compiler version being utilized in the deployment pipeline.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.