Skip to content

feat: Honor the FDv1 fallback directive in the orchestrator - #191

Draft
beekld wants to merge 3 commits into
bklimt/SDK-2753/fdv2-orchestratorfrom
bklimt/SDK-2865/fdv1-fallback-directive
Draft

feat: Honor the FDv1 fallback directive in the orchestrator#191
beekld wants to merge 3 commits into
bklimt/SDK-2753/fdv2-orchestratorfrom
bklimt/SDK-2865/fdv1-fallback-directive

Conversation

@beekld

@beekld beekld commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

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:

  • A non-zero TTL schedules a retry that returns to FDv2 once it elapses.
  • A zero TTL falls back indefinitely.

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.

@beekld
beekld force-pushed the bklimt/SDK-2865/fdv1-fallback-directive branch from 4b2a2b4 to 77e6614 Compare August 10, 2026 18:41
@beekld
beekld force-pushed the bklimt/SDK-2865/fdv1-fallback-directive branch from 77e6614 to e53c0cc Compare August 10, 2026 18:46
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