Entitlement checks must remain reliable even when entitlement data is missing or the Stigg API cannot be reached. When this happens—for example, if a new feature exists in code but has not yet been added to a plan, or during a temporary network outage—the SDK can fall back to predefined entitlement behavior. This allows your application to continue making access decisions rather than blocking the user experience.
You can define global fallback rules that specify how entitlements should behave when no valid data is available. These rules act as a safety net, ensuring features remain accessible (or restricted) according to your chosen defaults. When a fallback value is used, the SDK marks the response accordingly so you can log or monitor the event. Sidecar also exposes metrics that track fallback situations, such as failed network requests or cache misses.
Fallbacks can also be defined per feature. These override global settings and allow you to tailor behavior for specific entitlements—for example, permitting temporary unlimited usage for a critical feature or applying a stricter default for sensitive functionality.
While entitlement checks will continue to work offline, usage reporting is delayed until the SDK reconnects. Usage events are buffered in-memory and sent once connectivity is restored. If a persistent cache is available, the SDK can store these events safely to prevent data loss during long outages or process restarts.
