DPD Schedule Frequency & Approval Filtering

Changes to improve DPD claim processing speed and clean up stale reminder approvals.

Overview

Two related improvements:

1. DPD backfill schedule: Changed from once daily (11AM UK) to every 4 hours — new claims get picked up faster
2. Reminder filtering: Reminder approvals for resolved or DOR claims are now filtered out at the workflow and UI layers

Schedule Change

graph LR
    subgraph Before["Before"]
        A[11AM Daily<br/>CalendarSpec] --> B[Up to 24h delay]
    end

    subgraph After["After"]
        C[Every 4 Hours<br/>IntervalSpec] --> D[Max 4h delay]
    end

File: EmailProcessing.Worker/Program.cs — EnsureDpdBackfillScheduleAsync

• Create path: ScheduleIntervalSpec(Every: 4h) replaces ScheduleCalendarSpec at 11AM
• Update path: Now replaces existing.Spec with the new interval spec (previously preserved old spec)
• Existing schedules migrate automatically on next deploy
• ScheduleOverlapPolicy.Skip retained to prevent overlapping runs

DOR Reminder Filtering

DOR (Dispute of Resolution) statuses 17-20 are not terminal — claims may return from dispute resolution — but reminders are pointless while DOR is in progress. DOR is now filtered at the workflow and UI layers:

graph TB
    subgraph Workflow["Layer 1: Workflow Real-Time"]
        WF[IsClaimStatusRemindable]
        WF --> |"DOR detected"| SKIP[Skip reminder scheduling]
    end

    subgraph UI["Layer 2: UI Filter"]
        PA[PendingApprovalsService]
        PA --> |"DOR detected"| HIDE[Hide from approvals list]
    end

    subgraph Cleanup["Backfill Cleanup — unchanged"]
        CL[CleanupTerminalClaimsActivity]
        CL --> |"DOR is NOT terminal"| KEEP[Workflow stays running]
    end

    Workflow -.-> |"Prevents new approvals"| UI
    UI -.-> |"Hides stale approvals"| USER[User sees clean list]

Files Changed

Status Coverage

All statuses that suppress reminder approvals:

DOR claims keep their workflows running — the cleanup activity does not terminate them. If a DOR claim returns to a remindable status, reminders will resume automatically.

EmailSimulator Filtering Detail

sequenceDiagram
    participant UI as Approvals Panel
    participant SVC as PendingApprovalsService
    participant TC as Temporal Cloud
    participant DB as SQL Database

    UI->>SVC: GetPendingApprovalsAsync()
    SVC->>TC: ListWorkflowsAsync<br/>(HasPendingIntervention = true)
    TC-->>SVC: Workflow list with search attributes
    SVC->>DB: Batch query claim statuses<br/>for all tracking numbers
    DB-->>SVC: Current ClaimStatusId per claim
    SVC->>SVC: Filter out non-remindable statuses
    SVC-->>UI: Clean approval list

The DB query runs on every panel load — no caching — so status changes are reflected immediately.