{"@context":"https://schema.org","@graph":[{"@type":"WebPage","@id":"https://inquir.org/long-running-serverless-jobs#webpage","url":"https://inquir.org/long-running-serverless-jobs","name":"Long-running serverless jobs without HTTP timeouts","headline":"Long-running serverless jobs without HTTP timeouts","description":"Run long-running serverless jobs that outlast HTTP request windows—no timeout hacks, no worker servers. Move slow work to async pipelines with retries, execution history, and shared secrets beside your API endpoints.","inLanguage":"en-US","isPartOf":{"@id":"https://inquir.org/#website"},"author":{"@type":"Organization","name":"Inquir"},"datePublished":"2025-01-01T00:00:00.000Z","dateModified":"2026-04-20T00:00:00.000Z","citation":"https://inquir.org/docs"},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://inquir.org"},{"@type":"ListItem","position":2,"name":"Long-running serverless jobs","item":"https://inquir.org/long-running-serverless-jobs"}]},{"@type":"HowTo","@id":"https://inquir.org/long-running-serverless-jobs#howto","name":"Long-running serverless jobs without HTTP timeouts","description":"Run long-running serverless jobs that outlast HTTP request windows—no timeout hacks, no worker servers. Move slow work to async pipelines with retries, execution history, and shared secrets beside your API endpoints.","inLanguage":"en-US","author":{"@type":"Organization","name":"Inquir"},"step":[{"@type":"HowToStep","position":1,"name":"Return 202 from the HTTP handler","text":"Accept the request, validate input, trigger background processing with global.durable.startNew(), and return a job reference immediately."},{"@type":"HowToStep","position":2,"name":"Implement each slow step as a function","text":"Each pipeline step is a regular serverless function. Keep steps under 10 minutes; chain with dependsOn for sequencing."},{"@type":"HowToStep","position":3,"name":"Monitor via execution history","text":"See every step run, retry, and output in the console. Set duration SLO alerts so long jobs surface before customers notice."}],"isPartOf":{"@id":"https://inquir.org/long-running-serverless-jobs#webpage"}},{"@type":"FAQPage","@id":"https://inquir.org/long-running-serverless-jobs#faq","url":"https://inquir.org/long-running-serverless-jobs","isPartOf":{"@id":"https://inquir.org/long-running-serverless-jobs#webpage"},"mainEntity":[{"@type":"Question","name":"How long can an Inquir pipeline step run?","acceptedAnswer":{"@type":"Answer","text":"Each step is a serverless function invocation with its own configurable timeout—significantly longer than HTTP request windows. Chain multiple steps for work that needs hours. See docs for current limits."}},{"@type":"Question","name":"How do I track job status from the client?","acceptedAnswer":{"@type":"Answer","text":"Return a jobId from the 202 response. Poll a status endpoint that queries execution history, or have the final pipeline step post a webhook back to the client."}},{"@type":"Question","name":"What if a step fails mid-job?","acceptedAnswer":{"@type":"Answer","text":"Configure retry count and delay per pipeline step. Failed steps retry independently without restarting earlier steps. Set alerts on step failure rates to catch recurring issues."}}]}]}