Abhinav Raut 6c02431719 evaluate SLA synchronously on first reply, resolve and reopen ...

Met/breached timestamps were only stamped by the sweep tick, so a
"first response due soon" warning could go out after the agent had
already replied, and report averages measured tick time instead of
reply time.

Add EvaluateConversationSLA which judges the pending applied SLA right
away and always recomputes next_sla_deadline_at, so the conversation
package makes one call instead of pairing evaluate with a separate
recompute. ApplySLA reuses it for its pre-swap judgement. The sweep
loop stays as the breach detector for silent conversations and as the
retry net when the sync call fails.

2026-08-21 04:04:56 +05:30

..

models

recompute conversation SLA deadline when next response is settled

2026-08-21 02:01:04 +05:30

calculator_test.go

feat: test cases for SLA calculator, string utilities and attachments

2025-03-26 23:57:56 +05:30

calculator.go

fix[sla]: incorrect calculated deadline when SLA minutes ends exact at a working day's closing time.

2025-03-26 23:56:13 +05:30

queries.sql

clear sla deadlines on policy delete and stop double counting next response

2026-08-21 02:21:06 +05:30

sla_test.go

evaluate SLA synchronously on first reply, resolve and reopen

2026-08-21 04:04:56 +05:30

sla.go

evaluate SLA synchronously on first reply, resolve and reopen

2026-08-21 04:04:56 +05:30