Retry Oracle — Deterministic Retry and Spend Decisions avatar

Retry Oracle — Deterministic Retry and Spend Decisions

Under maintenance

Pricing

$2.00 / 1,000 useful retry decisions

Go to Apify Store
Retry Oracle — Deterministic Retry and Spend Decisions

Retry Oracle — Deterministic Retry and Spend Decisions

Under maintenance

Failed operation plus attempt, deadline, spend and idempotency context → RETRY, MUTATE or ABORT with reason codes, bounded delays and SHA-256 provenance. No LLM and no operation execution.

Pricing

$2.00 / 1,000 useful retry decisions

Rating

0.0

(0)

Developer

Dakota Myers

Dakota Myers

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

4 days ago

Last modified

Categories

Share

Retry Oracle

Give me a failed operation category and retry/spend context; receive RETRY, MUTATE, or ABORT with a deterministic reason code, delay, remaining budgets, policy version and input hash.

Scope and safety

This Actor advises only. It never executes retries, sends payments, changes credentials, or collects request payloads. Submit category labels and numeric context only; never send secrets or personal data. A non-idempotent failure always returns ABORT for reconciliation, even when a mutation is allowed. Unknown failures fail closed. Recommendations do not guarantee upstream success.

attemptNumber is the one-based failed attempt; maxAttempts is the total allowed count. deadlineSeconds is the total duration allowed since the operation began, while elapsedSeconds is duration already consumed. All spending fields use the same caller-selected currency. nextAttemptCost is an optional cost upper bound; omitting it cannot prove affordability of an unknown future price. Supply it when the next attempt costs money.

Transient failures use deterministic exponential backoff capped at 60 seconds, honoring a longer supplied Retry-After. A delay that reaches the deadline returns ABORT. The caller must enforce budgets at actual execution time and prevent concurrent retry storms; this stateless advisor cannot coordinate independent callers. MUTATE selects one explicitly allowed option and requires reassessment, without executing it.

Input and output

Submit 1–100 independent contexts in items. Fields: operationType, failureCategory, statusCode (optional), attemptNumber, maxAttempts, elapsedSeconds, deadlineSeconds, amountSpent, maxSpend, idempotent, allowedMutations; optional nextAttemptCost and retryAfterSeconds. Extra item fields are rejected. Invalid items are isolated and recorded by index in SUMMARY without echoing their data.

Dataset fields: decision, reasonCode, reason, recommendedDelaySeconds, selectedMutation, remainingAttemptBudget, remainingSpendBudget, policyVersion, inputHash, provenance, itemIndex. Identical valid context yields identical advice and hash. Hashes identify inputs; they are not encryption.

Billing

One decision-produced event only after each valid decision is saved. ABORT is a useful decision and is billable; invalid contexts are not charged. Platform costs are included. No automatic startup or dataset-item charge. Processing stops at the user spending limit.

Current price: USD $0.002 per useful decision saved. Platform costs are included.