Skip to main content

Inspectors Failure | Error : [Rule ID : ‘xxx’] External integration setup issue encountered

This article guides you through resolving the error message: [Rule ID: ‘xxx’] External integration setup issue encountered. This error occurs when an alert ticket is stuck in a failed state between Liongard and your PSA ticketing integration(Connectwise)

Updated over 3 weeks ago

Symptoms

  • A specific Inspector fails consistently.

  • The Inspector logs show the error: [Rule ID: ‘xxx’] External integration setup issue encountered.

Root Cause

This issue typically arises when an alert is triggered, but Liongard cannot successfully send the corresponding ticket to the integrated PSA system. This creates a blockage that prevents the Inspector from completing its run.

Resolution

Follow the steps below to identify and clear the stuck alert.

Step 1: Identify the Failing Rule

  1. Run the failing Inspector in Clear Cache + Debug mode.

  2. Copy the exact error message from the logs, including the Rule ID (e.g., [Rule ID: ‘184’]).

Step 2: Locate the Alert in the Environment

  1. Navigate to the Debug Logs for that system.

  2. In the Message column, search for the error message you copied.

  3. From the corresponding log entry, note the Rule Name (e.g., Processing Rule: 'xxxxxx').

Step 3: Find and Delete the PSA Ticket Link

  1. In a new browser tab, go to the Environment for the failing Inspector.

  2. Click on Overview and then Alerts (Open).

  3. In the table, search for the Rule Name from Step 2 in the Title column.

  4. Ensure the ConnectWise Ticket or IT Glue Ticket column is visible. If not, click the Columns button and enable it.

  5. In the row for the alert, locate the red Delete icon in the PSA Ticket column.

  6. Click the delete icon. A confirmation dialog will appear.

  7. Confirm the deletion. This breaks the link between the alert and the ticket in the PSA, allowing the Inspector to run again.

Step 4: Verify the Fix

  1. Return to the Inspector in Liongard.

  2. Run the Inspector again in Clear Cache + Debug mode.

  3. The Inspector should now complete successfully.

Important: If the error persists with a different Rule ID, this indicates another alert is stuck. Repeat Steps 1 through 4 for the new Rule ID until the issue is fully resolved.

Did this answer your question?