---
title: "How to fix bundler RPC errors"
description: "A guide to the list of Bundler RPC 32xxx errors and how to read them to resolve the errors."
---

# How to fix bundler RPC errors

This document provides a list of the JSON-RPC errors that you might encounter when using the [Bundler API](/bundler).

These are in addition to the [standard JSON-RPC error codes](https://www.alchemy.com/docs/reference/error-reference) returned by a bad method call.

## 32500: rejected by EntryPoint’s simulateValidation

The `userOp` is rejected by entryPoint's `simulateValidation`, during account creation or validation.

The `32500` error code may be accompanied by an additional [`AAxx` revert code](https://www.alchemy.com/docs/reference/entrypoint-v07-revert-codes) provided by the EntryPoint to give additional guidance.

**Data Fields**:

- `reason`: Optional string providing the main reason for the rejection.
- `inner\_reason`: Optional string providing additional details for the rejection.
- `revert\_data`: Optional bytes containing additional data related to the rejection.

## 32501: rejected by paymaster's validatePaymasterUserOp

The `userOp` is rejected by paymaster's `validatePaymasterUserOp`.

**Data Fields**:

- `paymaster`: Address of the paymaster.
- `reason`: String providing the reason for the rejection.

## 32502: opcode violation

The `userOp` does an Opcode violation or tries to access inaccessible storage.

Before submitting `userOps`, bundlers must make sure `userOps` don't grief the bundler by accessing banned opcodes when checking a signature.

**Data Fields**:

- `entity`: Type of entity \(e.g., paymaster, sender\) accessing the storage.
- `opcode`: Opcode that caused the violation.
- Additional fields \(when associated with `StakeTooLow`\):
  - `needs\_stake`: Entity that needs staking.
  - `accessing\_entity`: Type of entity accessing the storage.
  - `accessed\_address`: Address of the accessed storage.
  - `accessed\_entity`: Optional type of accessed entity.
  - `slot`: Storage slot accessed.
  - `minimum\_stake`: Minimum required stake.
  - `minimum\_unstake\_delay`: Minimum required unstake delay.

## 32503: out of time range

Either the account or the paymaster returned a time-range, and it is already expired or will expire soon.

**Data Fields**:

- `valid\_until`: Timestamp indicating the valid until time.
- `valid\_after`: Timestamp indicating the valid after time.
- `paymaster`: Optional address of the paymaster.

## 32504: throttled or banned

The `userOp` was rejected because the paymaster or aggregator is throttled or banned.

**Data Fields**:

- `entity`: Type of entity \(e.g., paymaster, aggregator\) that is throttled or banned.
- `address`: Address of the entity.

## 32505: stake or unstake-delay too low

The `userOp` was rejected because the paymaster's or [signature aggregator's](/overviews/account-abstraction-aggregate-signatures) stake or unstake delay was too low.

**Data Fields**:

- `needs\_stake`: Entity that needs staking.
- `accessing\_entity`: Type of entity accessing the storage.
- `accessed\_address`: Address of the accessed storage.
- `accessed\_entity`: Optional type of accessed entity.
- `slot`: Storage slot accessed.
- `minimum\_stake`: Minimum required stake.
- `minimum\_unstake\_delay`: Minimum required unstake delay.

## 32506: unsupported aggregator

The `userOp` was rejected because the wallet specified unsupported signature aggregator.

**Data Fields**:

- `aggregator`: Address of the unsupported aggregator.

## 32507: invalid signature

The `userOp` was rejected because it contains an invalid signature from the sender or the paymaster.

## 32521: execution reverted

The `userOp` was reverted during the execution phase. Link to a more detailed post

**Data Fields**:

- `revert\_data`: Optional bytes containing additional data related to the revert.

## 32602: invalid userOp

The `userOp` struct/fields sent to the bundler were invalid.

**Data Fields**:

- `current\_max\_priority\_fee`: Optional U256 containing the current maximum priority fee.
- `current\_max\_fee`: Optional U256 containing the current maximum fee.

## 32603: internal error

Internal JSON-RPC error. Please get in touch with our amazing support team.