Apify run-sync answers HTTP 408: why and what to change
The synchronous endpoint waits at most 300 seconds. After that it answers 408 while the run keeps going in Apify. Lower the result limit, or start the run asynchronously, wait for it to finish and then read its dataset.
Source: Apify API: run Actor synchronously and get dataset items. Applies to: n8n workflows, Apify API from code.
The question people ask
Why does the workflow or script stop with HTTP 408?
Where to fix it on this site
A known-good workflow to compare against: Google Maps leads to Google Sheets (validated, not run).
Related fixes
- Apify API 400, 401, 402 (x402) and 403: what each means
- n8n says Install this node to use it after import
- n8n HTTP Request times out before Apify answers
- Why does starting an Actor through the API return run information instead of scraped results
- Why are rows and hidden fields missing from my Apify dataset export
- Why does adding a request through the Apify API return an existing request ID