Skip to content

RUM-19232: Keep OpenFeature request failures recoverable - #4038

Draft
leoromanovsky wants to merge 1 commit into
developfrom
leo/rum-19232/openfeature-recoverable-errors
Draft

leoromanovsky wants to merge 1 commit into
developfrom
leo/rum-19232/openfeature-recoverable-errors

Conversation

@leoromanovsky

@leoromanovsky leoromanovsky commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

What does this PR do?

Map recoverable FlagsClientState.Error events to OpenFeature GeneralError. Preserve the error message and allow a later successful context update to restore Ready.

Motivation

A network failure without usable cached assignments currently changes OpenFeature status to Fatal. The native Flags client can recover. OpenFeature reserves PROVIDER_FATAL for irrecoverable failures.

Ref: RUM-19232

Additional Notes

Test coverage includes error messages, an unknown cause, and recovery through public OpenFeature status and flag evaluation. All 80 provider tests and 83 Flags single-FIT tests passed. The single-FIT regression uses the real Flags client and OpenFeature SDK with stub transport and storage; it fails on the previous implementation.

The Foundation documentation check could not run because the local FactoryKit runtime is unavailable.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Make sure you discussed the feature or bugfix with the maintaining team in an Issue
  • Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Map native Flags error states to GeneralError and verify recovery through OpenFeature status and flag evaluation.

Ref: RUM-19232
@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Pipelines  Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 71.69% (-0.18%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0d1a7e9 | Docs | View more details | Give us feedback!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant