Graceful 404/400 handling for optional entities in web extension#1481
Merged
amitjoshi438 merged 3 commits intomainfrom Feb 18, 2026
Merged
Graceful 404/400 handling for optional entities in web extension#1481amitjoshi438 merged 3 commits intomainfrom
amitjoshi438 merged 3 commits intomainfrom
Conversation
Sites without blogs, forums, or ideas provisioned return HTTP 400/404
from Dataverse when fetching these optional entity types. Previously
these were thrown and caught as system errors with message "{}",
producing ~5.4 false errors per session and degrading the read
completion rate from 97% to 77%.
Now, 400/404 responses for conditionalFolderEntities (blogs, blogposts,
ideas, ideaforums, forumannouncements, forumposts) are handled
gracefully with info telemetry instead of error telemetry.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
priyanshu92
approved these changes
Feb 16, 2026
ashwani123p
approved these changes
Feb 18, 2026
amitjoshi438
deleted the
users/amitjoshi/graceful-404-optional-entities
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fetchFromDataverseAndCreateFilesWebExtensionOptionalEntityNotFound) instead of throwing system errors with"{}"Changes
webExtensionTelemetryEvents.ts: AddedWEB_EXTENSION_OPTIONAL_ENTITY_NOT_FOUNDtelemetry eventremoteFetchProvider.ts: Added 400/404 check forconditionalFolderEntitiesbefore the generic!response.okthrow, usingbreakto exit the fetch loop gracefullyremoteFetchProvider.test.ts: Added 3 integration tests (404 on optional entity, 400 on optional entity, 404 on core entity still errors)CHANGELOG.md: Updated version to 2.0.132Test plan
npm run test-web-integration)🤖 Generated with Claude Code