feat: Honor the FDv1 fallback directive in the orchestrator - #191
Draft
beekld wants to merge 3 commits into
Draft
Conversation
beekld
force-pushed
the
bklimt/SDK-2865/fdv1-fallback-directive
branch
from
August 10, 2026 18:41
4b2a2b4 to
77e6614
Compare
beekld
force-pushed
the
bklimt/SDK-2865/fdv1-fallback-directive
branch
from
August 10, 2026 18:46
77e6614 to
e53c0cc
Compare
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.
Summary
An initializer or synchronizer can report an FDv1 fallback directive alongside its result. When the orchestrator sees one, it blocks the FDv2 sources and switches to the FDv1 fallback synchronizer. A directive takes precedence over a terminal error reported by the same source.
The directive carries a TTL, which the orchestrator honors:
The FDv2 spec describes the fallback as terminal, but the SDK follows the TTL instead. The retry runs on an independent timer, so it still fires when no synchronizer is available. Without that, an FDv1 fallback that itself hit a terminal error would strand the data system.