Template service is experiencing issues when marking templates as stable.

Summary

‌

On Nov 10th at 22:58UTC, Users were unable to save templates as a stable version. This issue affected a minor workflow. The failure occurred because the system attempted to construct a scopeInfo object with a null uniqueId when a feature flag (FF) was disabled. Since the template save path requires a valid uniqueId, the operation failed. Customers were advised to avoid this flow until a fix was deployed. A mitigation was applied the same day, and a permanent fix was later deployed to production.

Impact

• Template save operations that attempted to mark a template as “stable” failed.
• This affected a secondary, non-critical flow and in all environments where the Feature Flag was disabled while the new scopeInfo logic was active.

Root Cause

The failure occurred because scopeInfo was constructed with a null uniqueId when the relevant feature flag was disabled. A recent change introduced strict validation for uniqueId, which caused the template save operation to fail when provided with a null value.

Action Items

1. To prevent such issues happening we are enhancing our test coverage and feature flag coverage by:

   1. Adding validation at API boundaries to ensure uniqueId is always present or handled safely.
   2. Expand automated test coverage to include FF-on and FF-off scenarios for template save flows.
   3. Add guardrails and structured logging to detect null uniqueId cases earlier.