1

from this afternoon we receive the error in question from the api, without having changed anything after several months of use. Anyone have an idea why?

Improve this question

1 Answer 1

Reset to default
1

Error-Code 3040006's message is "Transaction Expiration Too Far"

What kind of client (cleos, eos-js, eos-sharp?) and what kind of network (EOS-mainnet, Telos, Wax?) are you using?

Default maximum transaction lifetime is 3600 seconds, therefore if expiration exceeds this maximum, you will get this error.

Here are the things I would do:

  1. Check if there are there any problems with the time on the machine(s) the transaction is sent from
  2. Check the transaction-expiration-field of the transaction(s).
  3. If you are using a private network, check if max-transaction-lifetime is set to a different value
Improve this answer
2
  • Thanks for the reply. The client is eos-js, the network the EOS-mainnet. We checked the server date and it's ok, and the transaction-expiration-field hasn't been changed, it's under 30 seconds
    – Marco
    Commented Jan 19, 2021 at 7:38
  • Have you tried pushing the transactions to a different node?
    – cmadh
    Commented Jan 19, 2021 at 19:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.