Breach time is not calculated as per the schedule defined on the SLA instead it is considering default 24/7 schedule
Release or Environment
The "task_sla" record and "schedule" are configured in different domains. Hence the "task_sla" record was not able to access the schedule, for this reason, the SLA is using a default schedule which is 24/7
To resolve this, Please configure the schedule on the same domain on which "task_sla" record will be created. In other words, "task_sla" record needs the visibility of the schedule that is defined on the SLA definition. Please refer below doc for more details.