Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6748 +/- ##
=======================================
Coverage 76.65% 76.65%
=======================================
Files 398 398
Lines 20108 20108
Branches 4844 4844
=======================================
Hits 15414 15414
Misses 4694 4694
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
hardillb
approved these changes
Feb 20, 2026
Steve-Mcl
reviewed
Feb 20, 2026
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
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.
Description
The Load Balancer (LB) occasionally delegates requests to stale or incorrect tunnel instances. Because the LB uses sticky sessions, once a "bad" path is established, subsequent requests fail until the affinity is reset.
Addresses the ~50% failure rate where the Load Balancer routes requests to improper tunnel backends. This PR introduces a retry mechanism that refreshes the device affinity token upon encountering an HTTP 502.
Statistical Impact (5 Attempts)
Initial Call 50%
Retry 1 75%
Retry 2 87.5%
Retry 3 93.75%
Retry 4 96.875%
Related Issue(s)
closes #6747
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel