stuntman / failures

Make the next call fail. Exactly as asked.

A rule says which requests, what to answer and how often. You, a test suite or an agent can turn it on, and the timeline marks every answer it changed.

How often is part of the rule.

  1. The first 2, then normal
  2. Every time
  3. Randomly, 25% of the requests

answered as the rule saysanswered normally

What you can provoke, line by line.

Arguments for every tool are in the tool reference.

LineToolsAnswers
HTTP APIsforce_answer · expire_tokensany named answer or SOAP fault; reset, empty, timeout, 500, 503, HTML; cut or slow streams; invalid tokens
AI modelsforce_ai_failure429, 500, 529, content filter, length, broken tool arguments, slow, cut
SMSforce_sms_failure · reply_sms_as_user500, 400, reset, empty, timeout; the person texts back
WhatsAppforce_whatsapp_failure · send_bad_webhook500, 400, reset, empty, timeout; wrong, missing or old signature, replay
Emaildecide_held · simulate_recipientdeliver, defer, bounce, drop; open, click, spam report, unsubscribe
Mailboxesset_mailboxlogin refused, busy, dropped fetch, TLS required, token expired
Storagecreate_rule · set_next_read · set_next_useany status, first N or a percentage; slow, truncated, bad MD5; bad links
Filesset_file_serverlogin refused, disk full, permission denied, cut halfway, slow, host key changed
Messagingset_next_delivery (namespace) · set_namespace_reachabilitylose lock, duplicate, hold, drop, dead-letter, out of order; refuse, busy
Streamsset_streams · rebalanceleader not available, SASL refused, slow fetch, duplicate, registry down; rebalance
Identityprovoke_sign_in · provoke_idpMFA, consent, user cancels, wrong tenant, expired, IdP down
Secretsprovoke_secret · provoke_key · provoke_certificate403, 404, 429, disabled, slow, expired, untrusted
Webhook inboxesset_inboxfail N times then succeed, delay, hang, redirect
Product eventsforce_events_failure400, 413, 429, slow, drop half
Telemetryprovoke_collector401, 403, 429, 503, refused, slow, drop half

A rule is a file, too.

Edit it in the UI and try it against the last 50 requests before saving. It is saved in storage/rules/<service>.yaml, and an agent creates the same rule with one tool call.

create_rule {
  "service": "azure-blob",
  "name": "Contract uploads fail twice",
  "when": {"op": "put", "container": "documents",
           "path": "contracts/**"},
  "then": {"respond": "503"},
  "how_often": {"first": 2}
}
The rule editor: when, then, how often and what the app will see
1When, then, how often

Which calls it catches, what they answer and for how many: try it against the last 50 requests before saving.

Callbacks your app must verify.

Stuntman signs callbacks the way each provider does: ECDSA for SendGrid, the app secret for Meta, HMAC for your own inboxes, and Stripe, Svix, GitHub or CloudEvents signatures for plugin webhooks. Ask for a badly signed, old, repeated or replayed one and check that your app rejects it.

send_bad_webhook {"kind": "wrong_signature"}
→ acme-api answered 401
Webhook deliveries with their signature checks and attempts