Workflow Troubleshooting
Diagnostic flow
Verified scenarios
- Workflow not visible: sidebar requires the correct audience/role plus an eligible session value; the direct route separately requires an eligible value.
- Definition cannot publish: the backend requires an existing definition and a valid publishable draft; the UI shows no preflight summary.
- Task cannot complete: the service returns conflict when the instance is not Running or the task is no longer Pending.
- Approval/rejection failure: reload the task list to detect a competing decision; the portal supplies a fixed comment.
- Delegation failure: a blank prompt submits nothing; the service also requires a nonblank target and pending task.
- Task not listed: the query matches only pending tasks assigned to the caller email or one of the caller's roles.
- Missing tenant context: the service translates the missing required tenant into a bad-request response.
- Health failure: distinguish basic process health from tenant health-data and from UI/API routing availability.
No verified operator replay, outbox-management, instance repair or task-reassignment console exists; escalation procedures require service-owner approval.
Requires Confirmation
Support escalation, approved recovery actions, log access, production routing and incident ownership require confirmation.
Source References
UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsxUI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsxmicroservices/src/workflow-service/Api/WorkflowEndpoints.csmicroservices/src/workflow-service/Application/Commands/WorkflowDefinitionCommands.csmicroservices/src/workflow-service/Application/Commands/WorkflowInstanceCommands.csmicroservices/src/workflow-service/Application/Queries/WorkflowQueries.cs
Related Articles
See Also
Keywords
Workflow troubleshooting, task conflict, tenant context, health.
Revision Information
Draft source-backed documentation reviewed on 2026-07-20; next quarterly review is 2026-10-20.