Hi   @karpuram sai di ,

This issue is typically related to ECC Queue processing in the target instance, rather than a problem with the Microsoft AD Spoke action itself.

The error:

“{sys_id_value} is not a valid sys_id of the discovery_status table”

indicates that something is interfering during ECC processing, which is why the Subflow remains in “In Progress” state.

What’s Happening

• Microsoft AD Spoke actions execute via MID Server → ECC Queue

• While processing ECC records, a Business Rule is invoking DiscoveryStatusMonitor

• This script expects a valid record in the discovery_status table

• An invalid value is being passed, causing a JavaScript exception

• Due to this failure, the ECC response is not completed → Flow gets stuck

Steps to Resolve

1. Check ECC Queue

• Navigate to: System Logs → ECC Queue

• Filter for:

  • State = Processing or Error

• Identify any stuck records related to your Subflow

2. Review Business Rules on ECC Queue

• Go to: System Definition → Business Rules

• Filter:

  • Table = ecc_queue

• Look for rules referencing:

  • DiscoveryStatusMonitor

  • agent_correlator

3.  Validate Discovery Configuration

• Ensure Discovery is properly set up in the target instance

• Check table:

  • discovery_status

• Confirm valid records exist

4.  Disable or Fix the Business Rule (Key Step)

• Temporarily disable the identified Business Rule on ecc_queue

• Re-run the Subflow

This typically resolves the issue if the rule is causing interference

5. Verify MID Server

• Ensure MID Server is:

  • Up and Validated

  • Has required capabilities (e.g., PowerShell/AD)

• Test with a simple AD action

6. Re-test the Subflow

• Re-publish the Subflow

• Execute again and verify it progresses past the AD step   

   

  
  
  If you find my response helpful or it resolves your issue, kindly mark it as Helpful and Accept the Solution.

  This helps others in the community quickly find the correct answer and improves overall knowledge sharing.

  Thank you for your support!