How does Nodinite detect when a Dynamics 365 workflow has failed?
Nodinite tracks Dynamics workflow state via 3 detection mechanisms:
Workflow status monitoring - Polls Dynamics 365 Web API every 60 seconds, retrieves workflow metadata including status: Running (workflow active and enabled), Stopped (workflow disabled or suspended), Draft (workflow not published), Suspended (workflow paused due to error or manual intervention). Alert triggers when: Workflow stops unexpectedly (Running → Stopped without scheduled maintenance window), workflow suspended (requires manual intervention).
Workflow execution history analysis - Polls workflow execution logs (last 100 executions per workflow), analyzes execution status: Succeeded, Failed, Canceled, In Progress. Alert triggers when: Error rate exceeds threshold (>5% of executions failed in last hour), consecutive execution failures (3+ errors in row), execution stuck (In Progress >10 minutes for workflow with 45-sec baseline).
Workflow performance monitoring - Tracks execution duration trends (12-month history), compares current execution time against baseline. Alert triggers when: Execution duration exceeds threshold (>2× baseline: 90 seconds for 45-sec baseline), execution duration increasing (8%+ weekly increase, statistically significant trend, projects timeout risk), execution timeout (>5 minutes = Dynamics workflow timeout limit).
Example alert: "Workflow: LoanApplicationProcessing | Status: Running | Last Execution: Failed | Error: System.TimeoutException: The operation has timed out | Executions last hour: 6 Succeeded, 4 Failed (40% error rate exceeds 5% threshold) | Execution duration: 4.8 min (baseline 45 sec, +640% increase) | Action: Investigate performance degradation, restart workflow via Remote Actions"
Related Questions
See all FAQs: [Troubleshooting Overview][]