Variable: SUBMISSION\_OUTCOME\_UNKNOWN\_REASONS
gSwap SDK 2.0.0-rc.4 / SUBMISSION_OUTCOME_UNKNOWN_REASONS
Variable: SUBMISSION_OUTCOME_UNKNOWN_REASONS
constSUBMISSION_OUTCOME_UNKNOWN_REASONS: readonly ["timeout","transport"]
Defined in: packages/gswap-sdk/dist/index.d.ts:258
Why the outcome of a write submission is unknown (SUBMISSION_OUTCOME_UNKNOWN.params.reason).
Both say the same thing about the swap (it MAY have been queued: never resubmit under a fresh
key, confirm error.uniqueKey instead) and differ only in what happened to the request.
timeout: the POST exceeded the gateway's timeout; the request may still be running.transport: the POST failed before an HTTP answer was read (offline, connection reset, DNS, CORS, a body that broke off). The bytes may have reached the server and been queued, so this does NOT prove the swap was not sent.