Accurate Error Tracking and Faster Timeouts
This release introduces a dedicated "rejected" status for billing-related events, ensuring you receive immediate feedback instead of waiting for unnecessary timeouts. We have also updated our documentation and error codes to help your automated integrations handle insufficient balance scenarios more reliably.
You will now receive specific error categories for SSL, DNS, and connection failures during the initial request phase. This prevents unnecessary processing on unreachable sites and provides clearer insights into why a scrape failed.
We corrected an issue where specific extraction requests were double-counted against your active limits, which previously led to premature rate-limiting errors. You can now reliably utilize your full concurrency quota.
We have introduced a distinct status for jobs that cannot proceed due to insufficient balance. This allows you to easily differentiate between account-level billing issues and genuine scraping failures.
Improvements
6Improved Network Error Clarity
You will now receive specific error categories for SSL, DNS, and connection failures during the initial request phase. This prevents unnecessary processing on unreachable sites and provides clearer insights into why a scrape failed.
Consistent Job Metadata Tracking
The domain field is now reliably included in all terminal job states, even for requests that fail due to insufficient credits. This ensures your data logs remain consistent and easier to audit across your entire request history.
General bug fixes and improvements
Plus 4 internal improvements for better reliability and performance.
New 'rejected' job status
We have introduced a distinct status for jobs that cannot proceed due to insufficient balance. This allows you to easily differentiate between account-level billing issues and genuine scraping failures.
Eliminated billing-related polling timeouts
Billing-rejected jobs now reach a terminal state immediately. Your applications will no longer hang or wait for the full timeout duration when your account balance is low.
Updated AI polling guides
Our technical documentation for AI-driven clients now includes the new terminal status indicators. This ensures your autonomous agents can correctly identify when to stop polling for results.
Bug Fixes
7Accurate Concurrency Limit Enforcement
We corrected an issue where specific extraction requests were double-counted against your active limits, which previously led to premature rate-limiting errors. You can now reliably utilize your full concurrency quota.
Reliable Billing Invoice Access
Invoice links in the billing dashboard now refresh automatically to ensure they remain accessible over time. This resolves an issue where older invoice documents would occasionally return expiration errors after 30 days.
Standardized Amazon Content Loading
Scraping behavior across Amazon domains has been standardized to ensure consistent content capture and reliable data extraction. This maintains stable performance while we perform further optimization benchmarks.
Precise Cache Management Controls
Targeted cache clearing now accurately respects all request parameters, ensuring only the intended data is refreshed. This provides finer control over your stored results and prevents accidental over-clearing of valid entries.
Improved billing error codes
Automated search requests now return a specific error discriminator for rejected jobs. This replaces misleading timeout messages with clear indicators of account balance issues.
Accurate batch processing status
Batch jobs containing rejected requests now resolve to a final status correctly. This fix prevents large batches from appearing stuck in a processing state indefinitely.
Corrected HTTP status codes
Synchronous requests now return the appropriate error codes when a job is rejected for billing reasons. This ensures your error-handling logic triggers correctly instead of receiving generic timeout responses.
Plus 6 internal changes for stability and performance.