From 24bbaed6ab1b570c9a263a8cfda62d480bad7139 Mon Sep 17 00:00:00 2001 From: Gitead Date: Thu, 30 Apr 2026 22:15:23 -0400 Subject: [PATCH] fix: invalidate appointments query after claim submitted via claims/preauth page When a claim was submitted through the claims/preauth page, the schedule page appointment color did not update because the appointments query cache was never invalidated after the selenium job completed. Added invalidation of QK_APPOINTMENTS_BASE in handleMHSeleniumPdfDownload so the schedule page refetches and reflects the new claim color. Co-Authored-By: Claude Sonnet 4.6 --- apps/Frontend/src/pages/claims-page.tsx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/apps/Frontend/src/pages/claims-page.tsx b/apps/Frontend/src/pages/claims-page.tsx index 6f4380d0..eb683e3c 100755 --- a/apps/Frontend/src/pages/claims-page.tsx +++ b/apps/Frontend/src/pages/claims-page.tsx @@ -22,6 +22,7 @@ import { useJobStatus } from "@/hooks/use-job-status"; import ClaimsRecentTable, { QK_CLAIMS_BASE, } from "@/components/claims/claims-recent-table"; +import { QK_APPOINTMENTS_BASE } from "@/pages/appointments-page"; import ClaimsOfPatientModal from "@/components/claims/claims-of-patient-table"; import { Claim, @@ -439,6 +440,8 @@ export default function ClaimsPage() { queryClient.invalidateQueries({ queryKey: ["groupPdfs"] }); queryClient.invalidateQueries({ queryKey: ["pdf-groups"] }); queryClient.invalidateQueries({ queryKey: ["claims-recent"] }); + // Invalidate appointments so the schedule page picks up the new claim color + queryClient.invalidateQueries({ queryKey: QK_APPOINTMENTS_BASE }); dispatch( setTaskStatus({