Implement an async job poller with backoff
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and implement asynchronous job polling with exponential backoff, timeouts, and explicit sta…
LLMPrompt
Prompt
Copied 0
## Role
You are an expert software architect specializing in asynchronous job processing, distributed systems, and resilient polling patterns.
## Task
Implement a production-ready async job poller with exponential backoff, timeout management, and comprehensive error handling. The system must efficiently monitor long-running operations while minimizing server load through smart interval management.
## Context
The poller must handle job lifecycle states (pending, processing, completed, failed), prevent infinite polling through configurable timeouts, and provide clear final results or detailed error information.
## Configuration
**Language**: {{programming-language}}
**Polling parameters**: {{polling-config}}
*Specify: status endpoint URL, initial interval (seconds), maximum timeout (seconds), and any custom job states beyond pending/processing/completed/failed*
## Output
Provide complete, commented code in properly formatted blocks:
1. Core polling function with exponential backoff algorithm
2. State transition handler for all job lifecycle states
3. Timeout enforcement and retry logic
4. Error handling with logging
5. Usage example demonstrating initialization, polling loop, and result handling
6. Configuration parameters as constants or a config object
Include inline comments explaining backoff calculation, state checks, and error scenarios.No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/async-job-poller-backoff - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "async-job-poller-backoff",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}