Problem
Policy compliance re-eval can return 503 when the retry worker is inactive, with no clear admin-visible degraded state.
What should be changed
- Health-check worker at boot; expose status on Policy Compliance page.
- Graceful messaging when re-eval is temporarily unavailable.
- Tests for inactive-worker path.
Expected outcome
Admins understand why compliance re-eval fails instead of seeing opaque errors.
Main files/areas likely affected
server/controllers/policyComplianceController.js, client/src/pages/PolicyCompliance.jsx, worker health endpoints
Why it matters
Operational transparency for compliance features.
{
"assignedAt": null,
"lastActivityAt": null,
"remindersSentAt": {},
"reminder12SentAt": null,
"reminder18SentAt": null,
"expiredAt": null,
"welcomeSentAt": null,
"welcomeSource": null,
"guidance": {},
"processedClaimCommentIds": [
5467351984
],
"processedUnclaimCommentIds": [],
"manualAssignment": false,
"authorPriorityExpiresAt": null
}
Problem
Policy compliance re-eval can return 503 when the retry worker is inactive, with no clear admin-visible degraded state.
What should be changed
Expected outcome
Admins understand why compliance re-eval fails instead of seeing opaque errors.
Main files/areas likely affected
server/controllers/policyComplianceController.js,client/src/pages/PolicyCompliance.jsx, worker health endpointsWhy it matters
Operational transparency for compliance features.
{
"assignedAt": null,
"lastActivityAt": null,
"remindersSentAt": {},
"reminder12SentAt": null,
"reminder18SentAt": null,
"expiredAt": null,
"welcomeSentAt": null,
"welcomeSource": null,
"guidance": {},
"processedClaimCommentIds": [
5467351984
],
"processedUnclaimCommentIds": [],
"manualAssignment": false,
"authorPriorityExpiresAt": null
}