open-feature / open-feature/flagd

Provider did not reconnect successfully within 5s. Emitting ERROR event...

Open
#2,053 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
997
Forks
136
Avg merge
4d 8h
Merged PRs (30d)
11

Description

We are getting intermittent errors while trying to fetch flags from AWS APpConfig. Please see logs with DEBUG enabled.

`
Sep 17, 10:37:30.002
INFO
2026-09-17T05:07:30.002Z debug http/http_sync.go:127 fetching configuration from http://localhost:2772/applications/ngcom-global-dev/environments/default/configurations/subscription {"component": "sync", "sync": "http"}

Sep 17, 10:37:30.002
INFO
2026-09-17T05:07:30.002Z debug http/http_sync.go:127 fetching configuration from http://localhost:2772/applications/ngcom-global-dev/environments/default/configurations/checkout {"component": "sync", "sync": "http"}

Sep 17, 10:37:32.207
INFO
Provider did not reconnect successfully within 5s. Emitting ERROR event...

`

Without Debug Flag enabled for Flags, below were the logs.

{"@timestamp":"2026-09-17T07:24:29.374Z","ecs.version":"1.2.0","log.level":"INFO","message":"Provider flagd transitioned from state READY to state STALE","process.thread.name":"openfeature-event-emitter-thread-84","log.logger":"dev.openfeature.sdk.FeatureProviderStateManager"} {"@timestamp":"2026-09-17T07:24:34.374Z","ecs.version":"1.2.0","log.level":"ERROR","message":"Provider did not reconnect successfully within 5s. Emitting ERROR event...","process.thread.name":"flagd-provider-thread-1","log.logger":"dev.openfeature.contrib.providers.flagd.FlagdProvider"} {"@timestamp":"2026-09-17T07:24:34.374Z","ecs.version":"1.2.0","log.level":"INFO","message":"Provider flagd transitioned from state STALE to state ERROR","process.thread.name":"openfeature-event-emitter-thread-84","log.logger":"dev.openfeature.sdk.FeatureProviderStateManager"} {"@timestamp":"2026-09-17T07:24:41.374Z","ecs.version":"1.2.0","log.level":"INFO","message":"Initializing sync stream observer","process.thread.name":"flagd-sync-retry-scheduler","log.logger":"dev.openfeature.contrib.providers.flagd.resolver.process.storage.connector.sync.SyncStreamQueueSource"} {"@timestamp":"2026-09-17T07:24:41.378Z","ecs.version":"1.2.0","log.level":"INFO","message":"Provider flagd transitioned from state ERROR to state READY","process.thread.name":"openfeature-event-emitter-thread-84","log.logger":"dev.openfeature.sdk.FeatureProviderStateManager"}

Does anybody has any idea about what could be the cause.

Below are the dependencies we are using

api 'dev.openfeature:sdk:1.20.1'
api 'dev.openfeature.contrib.providers:flagd:0.13.0'

and Flagd binary version is: v0.16.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the intermittent AWS AppConfig fetch failure with the listed Java dependencies and flagd v0.16.0, keeping DEBUG logging enabled. Inspect the HTTP fetch path shown at http/http_sync.go:127 and correlate it with the provider state transitions and reconnect timing. Done means the cause of the failed reconnect is isolated and a verified resolution or clearly documented reproduction is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go, java
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.