This changelog highlights releases that materially changed Instagram Followers Count Bulk Scraper for users. Dates use UTC; small internal refactors and routine maintenance are intentionally omitted.
Features
- Added an instant Standby API for one public Instagram profile or a bounded batch of up to three profiles while preserving the existing batch-run, dataset, scheduling, output, and pricing interfaces.
- Added typed HTTP errors, strict request/concurrency/time/response limits, and success-only idempotent per-profile charging for multi-tenant requests.
Reliability
- Intermittent API challenges and failed proxied profile embeds now get bounded embed recovery, including one final direct attempt instead of ending on a proxy error or throttle page.
Reliability
- Runs without access to the default SHADER proxy now try another available Apify proxy group, then use the public profile embed directly instead of silently repeating ineffective direct API requests.
- Unrecognized success responses and runtime proxy failures now enter bounded fallback recovery while preserving inspectable error rows and success-only profile charging.
Reliability
- Transient Instagram throttling now retries with fresh proxy sessions and a lightweight public-profile fallback instead of reusing a blocked identity.
- Runs now fail after saving diagnostic rows when every requested profile fails, preventing error-only datasets from appearing healthy.
Features
- Added public Store task examples so users can start common Instagram profile bulk-check workflows faster.
Pricing
- Updated tiered per-profile pricing so higher usage tiers receive progressively lower prices.
Features
- Initial release for bulk-checking public Instagram profile stats, including follower counts, following counts, post counts, verification status, biography, profile picture, and scrape status fields.
