DevelopersNode OperatorsMiners
Developers
Introduction
Cross-Chain Token Transfer
Introduction
Interchain Tokens
IntroductionCreate TokenUpgrade TokenInterchain Token ExecutableRate Limit
Developer Guides
Programmatically Create a TokenProgrammatically Create a Canonical TokenLink Custom Tokens Into Interchain Tokens
GlossaryRoadmap
General Message Passing
IntroductionExamplesSend MessagesSend Messages with TokensMonitor Transaction StateQuantum Portal ExecutableVerify GMP Transaction
Debug
Error MessagesDebug a Smart ContractFork Mainnet for Local TestingTransaction Recovery
Developer Guides
Cross-Chain Swaps with CCTPHello World GMP Example
Express Service
Quantum Portal SDK
IntroductionToken Transfer via Deposit AddressGMP Transaction Status and RecoveryQuantum Portal Query API
Indexers
IntroductionSubQuery
Chain and Contract Reference
Mainnet Chain NamesMainnet Contract AddressesTestnet Chain NamesTestnet Contract Addresses
QP DevToolsExamples
Contract and SDK reference
InterchainTokenServiceInterchainTokenFactoryTokenManagerQPGateway QPGasServiceQPExecutableQPJS SDK
Resources
Contract addresses
MainnetTestnet
RPCs
Ferrum Network
QP Explorer
How to use QP explorer
Bug Bounty

Execution error messages

There are two reasons that executions fail:

1. Insufficient gas to execute the transaction

If the prepaid gas is insufficient, you might see NOT ENOUGH GAS or other messages indicating the submitted gas is too low to execute, such as Insufficient gas for executing the transaction, intrinsic gas too low, etc.

There are two options to recover the transfer.

  1. Manually execute the payload at the destination chain via QPscan UI or QPJS SDK.
  2. Add more gas to the gas receiver on the source chain via QPscan UI or QPJS SDK.

2. Error in the destination contract logic

If the error is caused by the destination contract logic, you would see following the error message:

Transaction execution was reverted. Please check the implementation of the destination contract's _execute function.

What to do next: We suggest debugging your contract and then making a new call. You can try to follow the Debugging your smart contract guide.

ℹ️

The error message in reason: is extracted from the data returned by the Ethers.js library, from the data fields error.error.code and error.error.reason. The displayed error code (red tag) can be clicked to link to the description of each error code in Ethers.js’s official document.

ℹ️

If you get Nonce Expired or other messages indicating that nonce has already been used. It means that the nonce given in the transaction has already been consumed for the address on a blockchain. This error mostly happens when the same address submits multiple calls in a short period. We suggest you try manually executing it once again.

Edit this page
On this page