Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.biconomy.io/llms.txt

Use this file to discover all available pages before exploring further.

MEE supports time-bounded execution windows, enabling powerful UX patterns like scheduled actions, delayed bridging, market timing, and more.

​
What is Scheduled Execution?

With scheduled execution, you can define when a supertransaction is eligible to run using lowerBoundTimestamp and upperBoundTimestamp. Instead of executing immediately, you can defer execution, enforce expiration, or create precise windows of execution.

​
Use Cases

Scheduled Actions

Trigger transactions after a set delay—e.g. execute a trade 5 minutes from now

Custom Expiry

Keep retrying for a window, then discard if it still fails

Sequential Execution

Execute a series of transactions at fixed intervals

Per-Instruction Timing

Set different time bounds per instruction across chains

​
How It Works

Quote Created
    ↓
lowerBoundTimestamp reached → Execution becomes eligible
    ↓
MEE simulates and attempts execution
    ↓
upperBoundTimestamp reached → Quote expires if still failing
Timestamps are expected in seconds, not milliseconds. If both bounds are omitted, quotes execute immediately with a default 2-minute fallback.

​
Next Steps

Set Execution Time Bounds

Learn how to use global and instruction-level time bounds