ScrapeGraphAI v2.2.4: 2.2.4 (2026-09-07) Bug Fixes 🐛 read SCRAPEGRAPHAI_TELEMETRY_ENABLED from the environment, not the config file ( 8769c3b ) model
The official v2.2.4 release documents a concrete capabilities change. This update explains what changed from v2.2.4-beta.1, who should reassess the product, and what to verify next.
- What changed
- The official v2.2.4 release documents a concrete capabilities change. This update explains what changed from v2.2.4-beta.1, who should reassess the product, and what to verify next.
- Who is affected
- Evaluators, administrators, and workflow owners using ScrapeGraphAI where capabilities requirements affect adoption or deployment.
- What to do now
- Review the official v2.2.4 notes, test the affected capabilities workflow, and update the adoption decision if the result changes product fit.
The material change
Previously: {{agentName}} v2.2.2 documents this product change: 2.2.2 (2026-08-23) Bug Fixes fetch: surface HTTP errors and missing content instead of answering NA ( adc92f7 ), closes #1102 #1102
Now: ScrapeGraphAI v2.2.4 documents this product change: 2.2.4 (2026-09-07) Bug Fixes 🐛 read SCRAPEGRAPHAI_TELEMETRY_ENABLED from the environment, not the config file ( 8769c3b ) models: add Gemini 2.5 token limits so they are not truncated to 8192 ( c21af20 ) fetch: surface
This update covers the v2.2.4 release notes and does not infer behavior beyond the official release description.
What users should reconsider
The move from v2.2.4-beta.1 to v2.2.4 introduces a documented change that may alter operational compatibility.
The release has a versioned first-party source, so teams can verify the exact scope instead of relying on a generic monitoring excerpt.
Verify the affected workflow
- Review the official v2.2.4 notes, test the affected capabilities workflow, and update the adoption decision if the result changes product fit.
- Open the official source and verify the current product state.
- Review the current Agent Profile and affected Decision before acting.
Source-Backed does not mean execution-verified and does not establish comparative rank.
What was recorded before
{{agentName}} v2.2.2 documents this product change: 2.2.2 (2026-08-23) Bug Fixes fetch: surface HTTP errors and missing content instead of answering NA ( adc92f7 ), closes #1102 #1102
What is known now
ScrapeGraphAI v2.2.4 documents this product change: 2.2.4 (2026-09-07) Bug Fixes 🐛 read SCRAPEGRAPHAI_TELEMETRY_ENABLED from the environment, not the config file ( 8769c3b ) models: add Gemini 2.5 token limits so they are not truncated to 8192 ( c21af20 ) fetch: surface This update covers the v2.2.4 release notes and does not infer behavior beyond the official release description.
Accepted Change accepted:7013471f34b3561bb5baa12c46dbf116 · Agent Fact fact:7013471f34b3561bb5baa12c46dbf116 · Last verified 2026-09-07ScrapeGraphAI official releases
Published by ScrapeGraphAI. Evidence state remains Source-Backed; this is not execution verification.
Open official source →