Skip to content

Type Alias: ExecuteError

type ExecuteError = {
  description: string;
  revertData?: Bytes;
  stage: "simulate" | "submit" | "execute";
  status: Exclude<ExecuteStatus, typeof Success>;
};

Defined in: apps/submitter/lib/handlers/execute/types.ts:60

Failed execute call.

Properties

description

description: string;

Defined in: apps/submitter/lib/handlers/execute/types.ts:82

Description of the problem.

revertData?

optional revertData: Bytes;

Defined in: apps/submitter/lib/handlers/execute/types.ts:79

If the status string ends in "Reverted" or "Rejected", this will hold the associated revert or rejection data, if available.

Note that this will be different from the revert data of the simulation or onchain execution of the EVM tx that carried the boop, as first of all it might not have reverted (e.g. Onchain.ExecuteReverted does not cause the transaction to revert when executed onchain), and second we use carrier error to commit the errors back to the submitter.

TODO - Info about simulation vs execution (right now this is always simulation, but I think we can use an event to get this from execution too).

  • After, copy this docstring to the other revertData fields.

stage

stage: "simulate" | "submit" | "execute";

Defined in: apps/submitter/lib/handlers/execute/types.ts:64

Whether the error occurred at the simulation or execution stages.

status

status: Exclude<ExecuteStatus, typeof Success>;

Defined in: apps/submitter/lib/handlers/execute/types.ts:61