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

# Action Execution

> Reference for Web3 Action execution statuses (PENDING, SUBMITTED, SUCCEEDED, SKIPPED, FAILED, TIMED_OUT, RATE_LIMITED) and default runtime limits.

## Web3 Action Execution Status Types

Each execution of a [Web3 Action](/monitoring/web3-actions/introduction) carries one of the following statuses. The literals below are the values the API returns and the dashboard execution-history filter matches on; the dashboard may show a friendlier label (for example, "Success" for `SUCCEEDED`).

* **`PENDING`** - The execution has been created but not yet submitted. Manual runs and re-runs hold this status before submission.
* **`SUBMITTED`** - The execution has been submitted and is running. This status is temporary and changes once execution completes.
* **`SUCCEEDED`** - The execution completed without errors.
* **`SKIPPED`** - The execution was intentionally not run, typically because a condition or rule wasn't met.
* **`FAILED`** - The action code threw an error during execution.
* **`TIMED_OUT`** - The execution did not complete within the execution time limit (30 seconds by default).
* **`RATE_LIMITED`** - The trigger fired more often than the allowed rate. Rate-limited trigger events are dropped, not queued; the execution is not retried.
* **`TU_QUOTA_REACHED`** - The account's usage quota was exhausted when the trigger fired. The execution is dropped and not retried.

## Execution limits

Each execution runs with a 30-second time limit and 128 MB of memory by default.

<Note>
  If you need higher limits for your action execution, or if your action timed out, contact
  Tenderly support at [support@tenderly.co](mailto:support@tenderly.co).
</Note>

<Frame caption="Web3 Action Execution History">
  <img src="https://mintcdn.com/tenderly/FHtt5ZqGFmzL5kkh/images/web3-actions/action-execution-1.webp?fit=max&auto=format&n=FHtt5ZqGFmzL5kkh&q=85&s=c3e061aa7ac73bf4410b2d3f342a3785" alt="Web3 Action Execution History" width="1600" height="1000" data-path="images/web3-actions/action-execution-1.webp" />
</Frame>

## When an execution creates an incident

An incident is logged in [Error Reporting](/monitoring/web3-actions/references/error-reporting), and failure notification emails are sent, only when a trigger-based execution ends in `FAILED`. Manual runs never create incidents, regardless of outcome, and executions ending in `TIMED_OUT`, `RATE_LIMITED`, or `TU_QUOTA_REACHED` do not create incidents or send failure emails. Rate-limited executions are reported separately in a batched notification email, at most one per action per 24 hours (see [Usage Rate Limits](/monitoring/web3-actions/usage-rate-limits)).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.