> For the complete documentation index, see [llms.txt](https://glint-analytics.gitbook.io/glint-analytics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glint-analytics.gitbook.io/glint-analytics/querying-and-data-analysis/schema-reference/instructions-failed-table.md).

# Instructions Failed Table

| Name                      | Type            | Description                                                                                              |
| ------------------------- | --------------- | -------------------------------------------------------------------------------------------------------- |
| `BLOCK_SLOT`              | `FIXED`         | Slot number or identifier of the block.                                                                  |
| `TIMESTAMP`               | `FIXED`         | Raw value of the time in Unix Epoch time (in UTC time zone), which is then converted to DATETIME column. |
| `DATETIME`                | `TIMESTAMP_NTZ` | Timestamp of the transaction in UTC.                                                                     |
| `BLOCK_HASH`              | `TEXT`          | The hash of a specific block in the chain.                                                               |
| `BLOCK_HEIGHT`            | `FIXED`         | Indicates the numerical position of a block within the blockchain.                                       |
| `TRANSACTION_INDEX`       | `FIXED`         | The position or order of a transaction within a block of the blockchain.                                 |
| `TRANSACTION_ID`          | `TEXT`          | Identifier for the transaction that includes the instruction being tested.                               |
| `SIGNER`                  | `TEXT`          | n/a                                                                                                      |
| `SIGNERS`                 | `ARRAY`         | n/a                                                                                                      |
| `INSTRUCTION_INDEX`       | `FIXED`         | Index of instruction within a transaction.                                                               |
| `INNER_INSTRUCTION_INDEX` | `FIXED`         | Index of the inner instruction within a transaction.                                                     |
| `PARSED`                  | `VARIANT`       | Core information regarding the instruction.                                                              |
| `TYPE`                    | `TEXT`          | The type of instruction.                                                                                 |
| `PROGRAM`                 | `TEXT`          | Program or smart contract associated with the instruction.                                               |
| `PROGRAM_ID`              | `TEXT`          | The program ID of the instruction.                                                                       |
| `ACCOUNTS`                | `VARIANT`       | The accounts involved in the instruction.                                                                |
| `DATA`                    | `TEXT`          | The program input data encoded in a base-58 string.                                                      |
| `STACK_HEIGHT`            | `FIXED`         | The depth of the call stack during the execution of on-chain instructions.                               |
| `IS_TRANSFER`             | `BOOLEAN`       | Indicates whether the instruction involves a transfer.                                                   |
| `IS_MINT`                 | `BOOLEAN`       | n/a                                                                                                      |
| `IS_BURN`                 | `BOOLEAN`       | n/a                                                                                                      |
| `DATE_CREATED`            | `TIMESTAMP_NTZ` | Indicates the date in which the data was loaded.                                                         |
| `DATE_UPDATED`            | `TIMESTAMP_NTZ` | Indicates the date in which the data was updated.                                                        |

🔍 Use these columns to gather comprehensive insights into failed instructions. You can:

* Identify the block context using `BLOCK_SLOT`, `TIMESTAMP`, `DATETIME, BLOCK_HASH`, and `BLOCK_HEIGHT`.
* Determine transaction order with `TRANSACTION_INDEX` and `TRANSACTION_ID`.
* Examine signer details through `SIGNER` and `SIGNERS`.
* Trace the instruction’s execution sequence via `INSTRUCTION_INDEX` and `INNER_INSTRUCTION_INDEX`.
* Understand the core details of the instruction with `PARSED`, `TYPE`, `PROGRAM`, and `PROGRAM_ID`.
* Review the involved accounts using `ACCOUNTS` and the encoded input data via DATA.
* Assess execution depth with `STACK_HEIGHT`.
* Determine if the instruction involves a transfer using `IS_TRANSFER`.
* Evaluate data recency with `DATE_CREATED` and `DATE_UPDATED`.

For example, you might query `DATETIME`, `PROGRAM_ID`, and `STACK_HEIGHT` to pinpoint where a failure occurred and better understand its context.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://glint-analytics.gitbook.io/glint-analytics/querying-and-data-analysis/schema-reference/instructions-failed-table.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.