Troubleshooting Orphan Management in ConnectALL
search cancel

Troubleshooting Orphan Management in ConnectALL

book

Article ID: 399781

calendar_today

Updated On:

Products

ConnectAll On-Prem ConnectALL ConnectAll SaaS

Issue/Introduction

This article aims to compile some commonly encountered issues with Orphan Management in ConnectALL.

There are two categories of issues with ConnectALL Orphan Management:

  1. Items are not orphaned when expected
  2. Items are orphaned when not expected

 

Resolution

Items not Orphaned

Orphan Service is not Running

Ensure the Orphan service is running.

In Windows, check the status of the ConnectALL Orphan Management service in the services control panel applet

In Linux, check the status with:

$ sudo systemctl status connectall-orphan

 

Orphan Strategy is not Enabled

Edit the automation

Click the Orphan Management tab

Ensure the "Orphan Strategy" button is enabled on the upper right corner of the Orphan Strategy tab

 

Scheduled Run not yet Executed or not Enabled

Each automation can have schedules configured for how frequently they check for orphaned items and how far back the lookback window is.

Depending on your scheduled runs, the orphan service may not have executed for this automation yet.  If your schedule is configured to only run once every 24 hours, the time to discover orphaned items may not have passed yet.  Check your schedule to verify.

Additionally, Orphan management will only act on items that have been updated within the Scan Period.  The Scan Period is a period of time that ConnectALL uses as a guardrail to prevent querying for items created since the beginning of time and creating a high load on the target system.  If an item has not been updated within this Scan Period it will not be considered for orphaning.

Finally, the schedules themselves can be enabled and disabled, so ensure that the desired schedules are enabled.

 

Items Unexpectedly Orphaned

Added Flow Filter Constraint

If a flow filter constrains the results, items can be unexpectedly orphaned, particularly if there was an update to an existing Flow Filter that suddenly adds a new constraint that is applied to existing synched items.