Harness: FME SDKs - SDKs falling back to polling

What to do

Check whether you use Harness Streaming service. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 2h 4m it lasted.
Anything that failed between 2026-06-04 14:33 UTC and 2026-06-04 16:38 UTC may need a replay.
Subscribe to Harness's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=harness works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

identifiedJun 4, 2026, 2:33 PM UTC
Instability in streaming connections could cause a delay in propagating updates. All SDKs are designed to poll against the CDN on streaming disconnects and instability scenarios. This could also cause some noise in the logs as SDKs try to reconnect to streaming. But updates are unaffected.
provider
monitoringJun 4, 2026, 3:13 PM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedJun 4, 2026, 4:38 PM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Harness still down?

No, this incident was resolved 2026-06-04 16:38 UTC. For Harness's live state, see https://down.guide/harness.

How long did it last?

2h 4m, from 2026-06-04 14:33 UTC to 2026-06-04 16:38 UTC, by the times Harness posted.

What was affected?

Harness named Streaming service.

What caused it?

Harness hasn't published a root cause. If it does, it shows here.

Where does this come from?

Harness's official status page, https://status.harness.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.