afterQueued? | boolean | The write is ALREADY queued (the gateway acknowledged it with this uniqueKey), and what is being classified is a later step: confirming it, reading its apply result. Whatever the outcome, retryable is then false: a NEW request would be a second trade, so the app confirms the same key (or forgets it) and never offers "Try again". outcome is unchanged. The one exception is rejected: the chain evaluated the queued write and refused it (an apply result of Status: 0, CHAIN_REJECTED; a 422 dispatch). That PROVES it was not applied, so a new request under a fresh key cannot make a second trade, and retryable keeps the answer it has without this option (true). Every outcome that does not prove "not applied" (unknown, transient, not_queued, ...) is false. |