Dry-run a flow
Changed onSimulate this flow firing without storing events, enqueuing jobs, or consuming cooldown/rate-limit slots.
Works for every trigger activation type:
- event: validates the payload against the event catalog schema and evaluates the trigger conditions.
- custom: validates the payload against the custom payload schema (conditions do not apply).
- schedule: ignores the payload and reports the next fire time.
The response reports wouldFire — whether the flow would actually run right now — alongside the gates that decide it (enabled, device attached, blocked, cooldown). rateLimited is informational and is not folded into wouldFire.
Request
- Base URLhttps://api.mobilerun.ai
- URLhttps://api.mobilerun.ai/flows/{flowId}/dry-run
- AuthHTTP bearer
Path parameters
Request body
Response
Dry-run result
Changes
- breaking
removed the required property
from the response with the status - warning
added the new
integrations_apienum value to the///response property for the response status - info
added the required property
to the response with the status - info
added the required property
///to the response with the status - info
added the required property
///to the response with the status - info
added the required property
///to the response with the status - info
added the required property
to the response with the status
- breaking
- breaking
the request property
/became not nullable
- breaking