> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedera.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain.
> Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names.
> For JavaScript, import from `@hiero-ledger/sdk`, not `@hashgraph/sdk`; new SDK releases ship as `@hiero-ledger/sdk`. The Java SDK keeps the `com.hedera.hashgraph:sdk` Maven coordinates. Verify the exact import against the docs.
> Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural.
> Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case.
> For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias".

# ScheduleGetInfo

Gets information about a schedule in the network's action queue. Responds with INVALID\_SCHEDULE\_ID if the requested schedule doesn't exist.

## ScheduleGetInfoQuery

| Field | Type | Description |
| - | - | - |
| `header` | ​[QueryHeader](/reference/protobuf/miscellaneous/queryheader)​ | Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither). |
| `scheduleID` | ​[ScheduleID](/reference/protobuf/basic-types/scheduleid) | The ID of the Scheduled Entity |

## ScheduleInfo

Information summarizing schedule state.

| Field | Type | Description |
| - | - | - |
| `scheduleID` | [ScheduleID](/reference/protobuf/basic-types/scheduleid) | The id of the schedule |
| `creatorAccountID` | [AccountID](/reference/protobuf/basic-types/accountid) | The id of the account responsible for the service fee of the scheduled transaction |
| `payerAccountIDAccountID` | [AccountID](/reference/protobuf/basic-types/accountid) | The account which is going to pay for the execution of the scheduled transaction |
| `scheduledTransactionBody` | [SchedulableTransactionBody](/reference/protobuf/schedule/schedulabletransactionbody) | The scheduled transaction |
| `signers` | [KeyList](/reference/protobuf/basic-types/keylist) | The Ed25519 keys the network deems to have signed the scheduled transaction |
| `adminKey` | [Key](/reference/protobuf/basic-types/key) | The key used to delete the schedule from state |
| `memo` | string | The publicly visible memo of the schedule |
| `expirationTime` | [TimeStamp](/reference/protobuf/miscellaneous/timestamp) | The epoch second at which the schedule will expire |
| `scheduledTransactionID` | [TransactionID](/reference/protobuf/basic-types/transactionid) | The transaction id that will be used in the record of the scheduled transaction (if it executes) |
| `ledger_id` | bytes | The ledger ID the response was returned from; please see [HIP-198](https://github.com/hashgraph/hedera-improvement-proposal/blob/master/HIP/hip-198.md) for the network-specific IDs |
| **`oneof data`** : | | |
| `deletion_time` | [TimeStamp](/reference/protobuf/miscellaneous/timestamp) | If the schedule has been deleted, the consensus time when this occurred |
| `execution_time` | [TimeStamp](/reference/protobuf/miscellaneous/timestamp) | If the schedule has been executed, the consensus time when this occurred |

‌

## ScheduleGetInfoResponse <a href="#consensusgettopicinforesponse" id="consensusgettopicinforesponse" />

Response wrapper for the ScheduleInfo.

| Field | Type | Description |
| - | - | - |
| `header` | ​[ResponseHeader](/reference/protobuf/miscellaneous/responseheader)​ | Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither. |
| `scheduleInfo` | [ScheduleInfo](#scheduleinfo) | The information requested about this schedule instance |