Timeout  [Go SDK]

If you are encountering this error it means that either:

  • Frontier has not received a confirmation from the DigitalBits Core server that the transaction you are trying to submit to the network was included in a ledger in a timely manner.
  • Frontier has not sent a response to a reverse-proxy before a specified amount of time has elapsed.

The former case may happen because there was no room for your transaction for 3 consecutive ledgers. This is because DigitalBits Core removes each submitted transaction from a queue. To solve this you can:

  • Keep resubmitting the same transaction (with the same sequence number) and wait until it finally is added to a new ledger.
  • Increase the fee in order to prioritize the transaction.

This error returns a HTTP 504 Error.

Attributes

As with all errors Frontier returns, timeout follows the Problem Details for HTTP APIs draft specification guide and thus has the following attributes:

Attribute Type Description
type URL The identifier for the error. This is a URL that can be visited in the browser.
title String A short title describing the error.
status Number An HTTP status code that maps to the error.
detail String A more detailed description of the error.

Example

{
  "type": "https://digitalbits.org/frontier-errors/timeout",
  "title": "Timeout",
  "status": 504,
  "detail": "Your request timed out before completing.  Please try your request again. If you are submitting a transaction make sure you are sending exactly the same transaction (with the same sequence number)."
}

Edit this doc in GitHub

THE FUTURE OF LOYALTY STARTS HERE

Stay up to date on the latest happenings at DigitalBits. Get the latest news.