Skip to content

Main content

Random Webhook Retry Trace Generator

Generate synthetic webhook attempts under a supplied capped integer backoff policy with jitter, repeated delivery IDs, and success or nonretryable termination.

Loading tool…

Description

Generate synthetic webhook attempts under a supplied capped integer backoff policy with jitter, repeated delivery IDs, and success or nonretryable termination.

A protocol fixture is local test data representing headers, messages, identifiers, or request decisions. Serialization and parsing can be checked without contacting a server, while authentication, delivery, and actual client behavior require separate tests.

Generate synthetic webhook attempts under a supplied capped integer backoff policy with jitter, repeated delivery IDs, and success or nonretryable termination.

When to use this tool

Use this generator to create reproducible webhook retry trace cases from the supplied model or bank. Inspect the returned evidence before using cases in a test or exercise.

How to use the tool and how it works

  1. Supply deliveryId, statuses, retryStatusCodes, maximumAttempts, startMilliseconds, baseDelayMilliseconds, backoffFactor, maximumDelayMilliseconds, jitterMilliseconds in the field shapes below. Set seed when you need an explicit replay.
  2. Run the tool and correct any input error. For generated controls, distinguish a successful fixture containing an invalid case from failure to generate the fixture.
  3. Read attempts, termination. Use the conventions below and keep answer-bearing fields separate when presenting an exercise.

Draw an HTTP status for each attempt under a supplied retry-status set. Stop on success, nonretryable response or attempt exhaustion; otherwise schedule the next attempt using capped integer backoff plus nonnegative jitter and retain the same delivery ID and elapsed-time evidence.1

Delegated operations used for this result: status category; subtract two numbers. Their calculation or parsing conventions apply to the corresponding result fields.2, 3

Input fieldMeaning and unitsAccepted input
deliveryIdDelivery IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 96.
statusesStatusesRequired. Array of Safe integer; minimum 100; maximum 599.; minimum items 1; maximum items 128.
retryStatusCodesRetry Status CodesRequired. Array of Safe integer; minimum 100; maximum 599.; minimum items 0; maximum items 500.
maximumAttemptsMaximum AttemptsRequired. Safe integer; minimum 1; maximum 128.
startMillisecondsStart MillisecondsRequired. Safe integer.
baseDelayMillisecondsBase Delay MillisecondsRequired. Safe integer; minimum 0.
backoffFactorBackoff FactorRequired. Safe integer; minimum 1.
maximumDelayMillisecondsMaximum Delay MillisecondsRequired. Safe integer; minimum 0.
jitterMillisecondsJitter MillisecondsRequired. Safe integer; minimum 0.
seedOptional numeric seed; takes precedence over context randomness. Without either, use the fixed tool.io default seed.Optional. Safe integer.
Output fieldInterpretationReturned shape
attemptsAttemptsRequired. Array of Object; no unknown keys.; minimum items 1; maximum items 128.
attempts[].deliveryIdDelivery IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 128.
attempts[].attemptIdAttempt IdRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 128.
attempts[].attemptAttemptRequired. Safe integer.
attempts[].statusCodeStatus CodeRequired. Safe integer; minimum 100; maximum 599.
attempts[].categoryCategoryRequired. Text; maximum UTF-16 length 4096.
attempts[].timestampMillisecondsTimestamp MillisecondsRequired. Safe integer.
attempts[].elapsedMillisecondsElapsed MillisecondsRequired. Safe integer; minimum 0.
attempts[].elapsedFormattedElapsed FormattedRequired. Text; maximum UTF-16 length 4096.
attempts[].retryRetryRequired. Object; no unknown keys.
attempts[].retry.scheduledScheduledRequired. Boolean.
attempts[].retry.baseMillisecondsBase MillisecondsRequired. Safe integer; minimum 0.
attempts[].retry.jitterMillisecondsJitter MillisecondsRequired. Safe integer; minimum 0.
attempts[].retry.waitMillisecondsWait MillisecondsRequired. Safe integer; minimum 0.
terminationTerminationRequired. Text; one of "success", "nonretryable", "exhausted".
randomnessReplay metadata: source is seed or context; seed is the normalized 32-bit seed or null for a context source.Required. Object; no unknown keys.
randomness.seedOptional numeric replay seed; normalization and precedence are explained below.Required. Safe integer. or Null.
randomness.sourceSourceRequired. Text; one of "context", "seed".

An explicit safe-integer seed takes precedence over injected context randomness and is normalized to an unsigned 32-bit integer. With no seed and no context source, replay uses the fixed tool.io default seed. A context source must return finite values from zero inclusive to one exclusive; its advancing state must be retained separately. randomness records the source and normalized seed, or null for context. These generators are not cryptographic random sources.

json
{
  "input": {
    "deliveryId": "delivery-demo",
    "statuses": [
      500,
      502,
      204
    ],
    "retryStatusCodes": [
      500,
      502
    ],
    "maximumAttempts": 4,
    "startMilliseconds": 1000,
    "baseDelayMilliseconds": 1000,
    "backoffFactor": 2,
    "maximumDelayMilliseconds": 8000,
    "jitterMilliseconds": 100,
    "seed": 42
  },
  "output": {
    "attempts": [
      {
        "deliveryId": "delivery-demo",
        "attemptId": "delivery-demo/attempt-1",
        "attempt": 1,
        "statusCode": 502,
        "category": "Server Error",
        "timestampMilliseconds": 1000,
        "elapsedMilliseconds": 0,
        "elapsedFormatted": "0s",
        "retry": {
          "scheduled": true,
          "baseMilliseconds": 1000,
          "jitterMilliseconds": 45,
          "waitMilliseconds": 1045
        }
      },
      {
        "deliveryId": "delivery-demo",
        "attemptId": "delivery-demo/attempt-2",
        "attempt": 2,
        "statusCode": 204,
        "category": "Successful",
        "timestampMilliseconds": 2045,
        "elapsedMilliseconds": 1045,
        "elapsedFormatted": "1s",
        "retry": {
          "scheduled": false,
          "baseMilliseconds": 0,
          "jitterMilliseconds": 0,
          "waitMilliseconds": 0
        }
      }
    ],
    "termination": "success",
    "randomness": {
      "seed": 42,
      "source": "seed"
    }
  }
}

Limitations and assumptions

  • All timing is synthetic integer milliseconds. A retry policy is supplied by the caller and does not reproduce every provider’s delivery guarantees, network behavior or idempotency semantics.
  • A replay requires the same complete input and implementation. Randomized construction does not guarantee uniform coverage of every feasible output; finite samples can repeat unless a distinct-selection rule is explicitly stated.
  • The field tables state structural bounds; cross-field constraints and bounded search or output budgets also apply. Unknown keys are rejected where the object contract disallows them. Input errors are distinct from null fields and deliberate invalid controls in a successful output.

Alternative or Complementary methods

For a supplied example, inspect the returned construction or delegated check directly. To evaluate a consumer, also test cases chosen for its own boundaries; a generated finite corpus does not establish exhaustive coverage.

References

  1. Tool behavior and example: Random Webhook Retry Trace Generator — tool.io

  2. Calculation or validation: http/status-category — tool.io

  3. Calculation or validation: arithmetic/subtract-two-numbers — tool.io

Similar or alternative tools

  • Random HTML Attribute Quoting Corpus Generator

    Compose bounded benign start-tag source with caller text, delegated five-character entity escaping, feasible double/single/unquoted/Boolean attribute forms, and duplicate attributes; retain the lexical parser's raw character references and first-duplicate rule, not DOM-decoded values, sanitization, or HTML conformance certification.

  • Random HTML Boolean Attribute Fixture Generator

    Construct supported Boolean-attribute spellings with lexical parser outputs, separate presence-based interpretation and author-spelling keys, including the nonconforming false-value control.