# Network Response Messages

<table><thead><tr><th width="463">Network Response</th><th>Description</th></tr></thead><tbody><tr><td><code>INVALID_SCHEDULE_ID</code></td><td>The Scheduled entity does not exist; or has now expired, been deleted, or been executed</td></tr><tr><td><code>SCHEDULE_IS_IMMUTABLE</code></td><td>The Scheduled entity cannot be modified. Admin key was not set during the creation of the Scheduled entity.</td></tr><tr><td><code>INVALID_SCHEDULE_PAYER_ID</code></td><td>The provided Scheduled Payer does not exist</td></tr><tr><td><code>INVALID_SCHEDULE_ACCOUNT_ID</code></td><td>The Schedule Create Transaction TransactionID account does not exist</td></tr><tr><td><code>NO_NEW_VALID_SIGNATURES</code></td><td>The provided sig map did not contain any new valid signatures from required signers of the scheduled transaction</td></tr><tr><td><code>UNRESOLVABLE_REQUIRED_SIGNERS</code></td><td>The required signers for a scheduled transaction cannot be resolved, for example because they do not exist or have been deleted</td></tr><tr><td><code>UNPARSEABLE_SCHEDULED_TRANSACTION</code></td><td>The bytes allegedly representing a transaction to be scheduled could not be parsed</td></tr><tr><td><code>UNSCHEDULABLE_TRANSACTION</code></td><td>ScheduleCreate and ScheduleSign transactions cannot be scheduled</td></tr><tr><td><code>SOME_SIGNATURES_WERE_INVALID</code></td><td>At least one of the signatures in the provided sig map did not represent a valid signature for any required signer</td></tr><tr><td><code>TRANSACTION_ID_FIELD_NOT_ALLOWED</code></td><td>The scheduled and nonce fields in the TransactionID may not be set in a top-level transaction</td></tr><tr><td><code>IDENTICAL_SCHEDULE_ALREADY_CREATED</code></td><td>A schedule already exists with the same identifying fields of an attempted ScheduleCreate (that is, all fields other than scheduledPayerAccountID)</td></tr><tr><td><code>SCHEDULE_ALREADY_DELETED</code></td><td>A schedule being signed or deleted has already been deleted</td></tr><tr><td><code>SCHEDULE_PENDING_EXPIRATION</code></td><td>A schedule being signed or deleted has passed it's expiration date and is pending execution if needed and then expiration</td></tr><tr><td><code>SCHEDULE_FUTURE_GAS_LIMIT_EXCEEDED</code></td><td>The scheduled transaction could not be created because it would cause the gas limit to be violated on the specified expiration time</td></tr><tr><td><code>SCHEDULE_FUTURE_THROTTLE_EXCEEDED</code></td><td>The scheduled transaction could not be created because it would cause throttles to be violated on the specified expiration time</td></tr><tr><td><code>SCHEDULE_EXPIRATION_TIME_MUST_BE_HIGHER_THAN_CONSENSUS_TIME</code></td><td>The scheduled transaction could not be created because it's expiration_time was less than or equal to the consensus time</td></tr><tr><td><code>SCHEDULE_EXPIRATION_TIME_TOO_FAR_IN_FUTURE</code></td><td>The scheduled transaction could not be created because it's expiration time was too far in the future</td></tr><tr><td><code>SCHEDULE_EXPIRY_MUST_BE_FUTURE</code></td><td>A 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</td></tr><tr><td><code>SCHEDULE_EXPIRY_TOO_LONG</code></td><td>A 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 </td></tr><tr><td><code>SCHEDULE_EXPIRY_IS_BUSY</code></td><td>A 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</td></tr></tbody></table>
