Server 1.191.4 improves remote cache rollout reliability and tightens automation scheduling.
Remote cache rollouts
- Remote cache servers now stay active during background rollouts, and new endpoints are only exposed after both DNS and HTTPS readiness checks pass. This prevents the CLI from trying to use a cache node before TLS and DNS propagation are complete.
- You can add extra Kura cache regions from account settings, and internal provider details are no longer shown in the customer-facing server list.
Automation scheduling
- Automation scheduler jobs are now deduplicated while queued or running, so overlapping scheduler ticks no longer stack up into evaluation backlogs.