APEX FLOW WEB SCRAPER / REFERENCE LIBRARY
Diagnosing an empty scraping result
An empty result can come from access failure, missing rendering, a broken selector or a genuinely empty source. Check these causes before changing the recipe.
Start with the response
Inspect status, final URL, content type and challenge indicators. A login page or block screen can return 200. Treat that as a different outcome from a valid target document.
Then inspect the content
If the raw HTML is an application shell, try rendering on a small sample. If the content exists but the field is missing, inspect selector matches. If the selector finds multiple values, narrow its scope instead of taking an arbitrary match.
Use lifecycle evidence
Check deadline, byte budget, worker heartbeat and cancellation state. A job stopped at a resource limit can have useful partial results. A worker that is not running cannot make progress no matter how good the selector is.
Document the repair
Save the old recipe, the example URL and the failure reason. Test the revised recipe against both the broken page and a previously working page. This release does not automatically rewrite recipes or claim self-healing extraction.
← All reference articles · Current capabilities and limits →