Skip to main content
Network ResponseDescription
INVALID_SCHEDULE_IDThe Scheduled entity does not exist; or has now expired, been deleted, or been executed
SCHEDULE_IS_IMMUTABLEThe Scheduled entity cannot be modified. Admin key was not set during the creation of the Scheduled entity.
INVALID_SCHEDULE_PAYER_IDThe provided Scheduled Payer does not exist
INVALID_SCHEDULE_ACCOUNT_IDThe Schedule Create Transaction TransactionID account does not exist
NO_NEW_VALID_SIGNATURESThe provided sig map did not contain any new valid signatures from required signers of the scheduled transaction
UNRESOLVABLE_REQUIRED_SIGNERSThe required signers for a scheduled transaction cannot be resolved, for example because they do not exist or have been deleted
UNPARSEABLE_SCHEDULED_TRANSACTIONThe bytes allegedly representing a transaction to be scheduled could not be parsed
UNSCHEDULABLE_TRANSACTIONScheduleCreate and ScheduleSign transactions cannot be scheduled
SOME_SIGNATURES_WERE_INVALIDAt least one of the signatures in the provided sig map did not represent a valid signature for any required signer
TRANSACTION_ID_FIELD_NOT_ALLOWEDThe scheduled and nonce fields in the TransactionID may not be set in a top-level transaction
IDENTICAL_SCHEDULE_ALREADY_CREATEDA schedule already exists with the same identifying fields of an attempted ScheduleCreate (that is, all fields other than scheduledPayerAccountID)
SCHEDULE_ALREADY_DELETEDA schedule being signed or deleted has already been deleted
SCHEDULE_PENDING_EXPIRATIONA schedule being signed or deleted has passed it’s expiration date and is pending execution if needed and then expiration
SCHEDULE_FUTURE_GAS_LIMIT_EXCEEDEDThe scheduled transaction could not be created because it would cause the gas limit to be violated on the specified expiration time
SCHEDULE_FUTURE_THROTTLE_EXCEEDEDThe scheduled transaction could not be created because it would cause throttles to be violated on the specified expiration time
SCHEDULE_EXPIRATION_TIME_MUST_BE_HIGHER_THAN_CONSENSUS_TIMEThe scheduled transaction could not be created because it’s expiration_time was less than or equal to the consensus time
SCHEDULE_EXPIRATION_TIME_TOO_FAR_IN_FUTUREThe scheduled transaction could not be created because it’s expiration time was too far in the future
SCHEDULE_EXPIRY_MUST_BE_FUTUREA scheduled transaction configured to wait for expiry to execute was given an expiry time not strictly after the time at which its creation reached consensus
SCHEDULE_EXPIRY_TOO_LONGA scheduled transaction configured to wait for expiry to execute was given an expiry time too far into the future after the time which its creation reached consensus
SCHEDULE_EXPIRY_IS_BUSYA scheduled transaction configured to wait for expiry to execute was given at a time which there is already too many transactions scheduled to expire; its creation must be retried with a different expiry time