fixes

fivetran · Jan 24, 2024 · 05455d2 · 05455d2
1 parent 2e87000
commit 05455d2
Show file tree

Hide file tree

Showing 5 changed files with 4 additions and 4 deletions.
diff --git a/docs/catalog.json b/docs/catalog.json
diff --git a/docs/graph_summary.json b/docs/graph_summary.json
diff --git a/docs/manifest.json b/docs/manifest.json
diff --git a/docs/run_results.json b/docs/run_results.json
diff --git a/models/sla_policy/reply_time/int_zendesk__reply_time_combined.sql b/models/sla_policy/reply_time/int_zendesk__reply_time_combined.sql
@@ -121,7 +121,7 @@ with reply_time_calendar_hours_sla as (
         agent_reply_at >= sla_schedule_start_at and agent_reply_at <= sla_schedule_end_at) -- ticket is replied to between a schedule window
         or (agent_reply_at < sla_schedule_start_at and sum_lapsed_business_minutes_new = 0 and sla_breach_at = first_sla_breach_at) -- ticket is replied to before a schedule window and no business minutes have been spent on it
         or (agent_reply_at is null and {{ dbt.current_timestamp() }} >= sla_schedule_start_at and ({{ dbt.current_timestamp() }} < next_schedule_start or next_schedule_start is null)) -- ticket is not replied to and therefore active. But only bring through the active SLA record that is most recent (after the last SLA schedule starts but before the next, or if there does not exist a next SLA schedule start time)  
-        or (agent_reply_at > sla_schedule_end_at and agent_reply_at < next_schedule_start ) -- ticket is replied to outside sla schedule hours
+        or (agent_reply_at > sla_schedule_end_at and (agent_reply_at < next_schedule_start or next_schedule_start is null)) -- ticket is replied to outside sla schedule hours
       ))
     or not in_business_hours