How to Stop SLA Milestone Clock After Working Hours in Oracle Fusion Service?

Hi Oracle Community,

We are facing a major issue with engineer clock stopped if 9-5pm working coverage timing in Oracle Fusion CX Service.

Our SLA/Asset coverage schedule is set to 9AM–5PM, Mon–Fri, and we have assigned this schedule to our SLA properly using the "Manage Coverage Schedules" and "Manage Service Level Agreements" setups.

However, even though the schedule is assigned, the milestone clock (e.g., First Response) keeps running outside working hours including overnight and weekends which causes false SLA breach alerts.

Example:
If an SR is created at 4PM and the work engineer is done from 4pm to 5pm then the next day his clock starts from 9am thats is what we expect and need;