Docs

Runrail Public Beta Limits And Safety

Runrail Public Beta runs on Base Sepolia with explicit transaction, schedule, gas, retry, quota, rate, and custody limits. Review these limits before funding an Execution wallet or activating a job.

Network And Funds

  • Base Sepolia only, chain ID 84532.
  • Testnet use only; no Base mainnet, other mainnet, or multi-chain execution.
  • Transaction value is always 0.
  • You fund your dedicated Execution wallet with Base Sepolia test ETH.
  • Do not send production funds or valuable assets to an Execution wallet.
  • Public Beta does not include billing, a service fee, production support, or an SLA.

Testnet behavior, simulation, and past execution do not guarantee a future transaction or establish production suitability.

Identity And Execution-Wallet Custody

Your injected EOA wallet signs a SIWE identity message. It identifies your Runrail workspace but does not sign or submit scheduled transactions.

Each workspace has a separate Execution wallet operated by Runrail. You can inspect its address, lifecycle, balance, and readiness but do not receive its private key. Runrail does not fund ordinary execution.

Job Definition Limits

  • The target must be a nonzero 20-byte EVM address on Base Sepolia.
  • Calldata must use a lowercase 0x prefix followed by an even number of hexadecimal characters. Empty 0x is valid. Decoded calldata may be at most 8,192 bytes.
  • The job-create request body may be at most 32,768 bytes.
  • Start time must be from 120 seconds to 31,536,000 seconds in the future.
  • Interval must be from 900 to 31,536,000 seconds.
  • A scheduled slot receives at most 3 attempts: one initial attempt and up to 2 retries.
  • Target, calldata, schedule, network, value, and retry policy cannot be edited. Archive the job and create a replacement to change its definition.

Runrail does not provide a target allowlist, function-selector allowlist, ABI validation, or workflow builder. Verify the target and calldata yourself. Runrail does not audit or guarantee the contracts you call.

Job Quotas

  • At most 10 non-archived jobs per workspace.
  • At most 20 successful job creates per workspace in a rolling 24-hour period. Archived jobs still count toward this rolling limit.
  • At most 3 active jobs per workspace.
  • At most 100 active Public Beta jobs across the service.

Creating a job requires a workspace-scoped idempotency key that remains active for 24 hours. A same-request replay does not create another job or consume another create unit.

Readiness, Simulation, And Gas

Readiness is ready, not_ready, or unknown. Runrail checks the Execution wallet and its Base Sepolia test ETH, target code, exact call simulation, gas estimate, schedule, quotas, and safety controls.

Runrail simulates when a job is activated and before each new attempt. A successful simulation is a current check, not a guarantee of execution. A deterministic simulation failure stops that scheduled attempt; temporary failures may retry within the three-attempt cap.

Estimated gas receives 20% padding. The padded gas limit may not exceed 1,500,000. Users cannot override gas or fee settings. Funding readiness is calculated from the next attempt's estimated gas and fee policy rather than a fixed ETH minimum.

unknown fails safely for new work. Already submitted transactions continue to confirmation and reconciliation when readiness changes.

Lifecycle And Execution Outcomes

  • A new job is inactive until you activate it.
  • Pause stops future scheduled work.
  • Resume performs a complete readiness check and continues at the next future slot; missed slots are not backfilled.
  • Archive is irreversible, removes the job from normal lists, and preserves execution and receipt history.
  • If scheduled work is still waiting to start 300 seconds after its scheduled time, Runrail records it as not executed.

Submission is not success. Success requires confirmation. History may show waiting, submission, confirmation, retry, confirmed, reverted, exhausted, skipped-by-policy, or failed-precondition outcomes, with receipts, hashes, and explorer links when applicable.

Request Rates And Pagination

  • Authenticated reads: 120 per workspace per minute.
  • Mutations: 20 per workspace per minute and 100 per workspace per hour.
  • These quotas and rate limits are shared by the App session and every API credential for the workspace.
  • Rate-limited requests return HTTP 429 with Retry-After.
  • Job and execution-history pages default to 25 items and accept at most 100.

API Credential Safety

Create credentials only through API Access in the App. Plaintext is shown once and cannot be recovered. Store it as a secret and use it only at https://api.runrail.app/v1.

  • At most 3 credentials may be active per workspace.
  • At most 10 successful credential creates are allowed per workspace in a rolling 24-hour period.
  • Revocation is permanent.
  • Signing out or browser-session expiry does not revoke credentials.
  • A frozen workspace may list and revoke credentials but cannot create one.
  • App browser sessions and API bearer credentials are not interchangeable.

If credential creation has an unclear result, do not repeat it automatically. Refresh non-secret metadata, revoke any possible unknown credential, and explicitly create a replacement only if needed.

Safety Controls

Runrail safety controls can prevent new affected work when safety is uncertain. They do not erase history or rewrite terminal outcomes.

Transactions already submitted to Base Sepolia continue through confirmation and reconciliation.

Security Reporting

Report suspected vulnerabilities or security issues to security@runrail.app. Do not include private keys, bearer credentials, session material, wallet signatures, or other secrets in a report.

Privacy, Retention, And On-Chain Data

Transactions, calldata, wallet addresses, and explorer evidence may be permanent and publicly observable. Do not put secrets or unnecessary private information in calldata, screenshots, logs, issue reports, or support material.

Signing out or clearing browser state does not delete your workspace, jobs, Execution-wallet state, execution history, API credentials, or public on-chain data. Public Beta does not provide self-service deletion or export.

  • Consumed or expired SIWE challenge records are deleted 30 days after consumption or expiry.
  • Revoked or expired session records are deleted 30 days after revocation or expiry.
  • Job-create idempotency records expire after 24 hours and are deleted 30 days later.

These periods do not claim deletion of workspace identity, jobs, attempts, receipts, transaction hashes, public on-chain records, key-recovery state, or required safety records. Provider backups follow their own lifecycle.

Acceptable Use

Do not use Runrail for illegal or abusive activity, system compromise, quota or safety-control evasion, interference with service operation, misuse of third-party contracts or assets, or submission of secrets and unnecessary private information.

Not Included

Public Beta does not include public run-now, webhooks, caller-defined retry policy, nonzero transaction value, mainnet, multi-chain execution, billing, OAuth, organizations, teams, RBAC, an SDK program, a developer portal, wallet linking, self-service identity recovery, user access to Execution-wallet private keys, general workflow automation, production support, or an SLA.

See App Usage and Runrail API Usage.

Back to docs index