- 2 minutes to read

Microsoft Dynamics 365, FAQ, Troubleshooting, Common Questions Microsoft Dynamics 365, FAQ, troubleshooting, common questions Can Nodinite automatically restart failed Dynamics 365 workflows?

Can Nodinite automatically restart failed Dynamics 365 workflows?

Can Nodinite automatically restart failed Dynamics 365 workflows?

Yes, via Auto-Healing feature. Configure automatic remediation actions when specific alerts fire:

Example 1: Auto-restart transient workflow failures

  • Alert: Workflow "LeadAssignment" execution error with message contains "SocketException: Connection refused" or "TimeoutException"
  • Auto-Healing Action: Wait 2 minutes (allow transient network issue or Dynamics service interruption to resolve), restart workflow via Remote Actions, if still failing after restart → escalate to PagerDuty

Example 2: Auto-enable suspended workflows after business hours

  • Alert: Workflow status = "Suspended" longer than 30 minutes outside scheduled maintenance window (Suspended state indicates workflow paused due to error or manual intervention)
  • Auto-Healing Action: Check workflow execution history (if last 5 executions all Succeeded before suspension, likely transient issue), re-enable workflow via Remote Actions, send notification to operations (workflow auto-enabled, monitor for recurrence)

Example 3: Auto-alert license threshold breach

  • Alert: Inactive user count >10% of total licenses (87 inactive users / 450 total = 19.3% waste threshold)
  • Auto-Healing Action: Generate license optimization report (list inactive users + last login dates + license cost), email to IT management + Finance (actionable recommendations: deprovision 87 users = $99K annual savings), schedule follow-up alert in 30 days if no action taken

Safety guardrails: Auto-Healing includes limits to prevent runaway automation: Maximum 3 restart attempts per hour per workflow (prevent infinite restart loop if problem not transient), require approval for production actions (auto-restart in Sandbox/UAT, approval required for Production), complete audit trail (every Auto-Healing action logged with timestamp + trigger alert + action result).

Configuration: Web Client → Settings → Auto-Healing Rules → Add Rule → Select alert type (Dynamics workflow error) → Configure action (Restart workflow) → Set conditions (error message contains "TimeoutException") → Set limits (max 3 restarts/hour) → Save.

See all FAQs: [Troubleshooting Overview][]