0
Under review

Link Synchronization not triggering

Hayden Gray 3 months ago in UNIFYBroker Service updated by Matthew Davis (Technical Product Manager) 3 months ago 1

In UNIFYConnect test environment when attempting to perform a baseline synchronisation or delta changes synchronisation, the buttons seemingly do nothing when attempting to trigger on the link. The link is between a CSV connector/adapter and a locker with about ~10k entities. Nothing else is currently running, all other link schedules are disabled and no connectors are importing, nor are any change reflect options are running. 

When I click a button to sync the page refreshes like it has executed but nothing else happens. Nothing appears under the "Recent Jobs" section of the link page and it logs 2 messages in the log:

23/Jan/2024 23:29:28
Information
Link Request to manually queue a baseline synchronization job on link started.
Request to manually queue a baseline synchronization job on link Managed User > AD User started.
23/Jan/2024 23:29:28
Information
Link Request to manually queue a baseline synchronization job on link completed.
Request to manually queue a baseline synchronization job on link 'Managed User > AD User' completed. Duration: 00:00:00.0310830

Is there a way I can see what is stopping the sync operation from executing? Let me know if you need more information.

Thank you

Under review

Hey Hayden,

The log messages you're seeing are for the job being queued, not actually executed. We've noted that in v5.3 the queue operation can take some time, so you'll likely see some log messages about the actual task being executed a short time after.

As we discussed on the phone too, be conscious that schema fields being mapped purely in powershell tasks (and not through normal entity mapping means) may not behave as expected, particularly in changes sync scenarios. The change detection engine relies on the link mappings to determine whether a change in an adapter (or a locker) should be flagged for a link, so for fields not mapped these changes will not be triggered.