Hi Michal.

Not enough information to guess at what might be happening.

You can enable trace logging (see documentation) and check the logs.
You can check the cross-references for this item.
Or you can create a support case to receive assistance.

Best,
Dom.

Hi Dominique,

there is nothing else to share as it is black box. Integration for particular items stop to works randomly. Once se restart a service, items which were not synchronized are synchronized correctly. We did not find any logic whet integration stop to works but for some items forks all the time correctly.

Thank you for advice toenable trace log level

We created and case to Opan text and added trace logs.

What's the case number, please?

We are seeing somewhat similar behavior with our ALM defect to Jira bug integration using MF Connect 4.4.3. 
At the start of each day, updates to existing ALM defects are not updating Jira bugs, however Jira bug updates are updating ALM defects.  

IE:  Yesterday we submit 5 ALM defects that create 5 Jira bugs.  All updates to the defects or bugs synch fine during that day. 
The next day we update one of these ALM defects and update one of these Jira bugs. 
The ALM defect updates are not updating the Jira bug.  The Jira bug updates are updating the ALM defect.
A newly submitted ALM defect will create a new Jira bug and all updates are fine.  Existing defects are not.

We run the MF Purge job nightly and have tried various rules but no luck.  We will open a case w/Open Text to review further.

Hi, it is 02813292.

Connect 24.1.1 was released March 13.
It should address your issue (according to analysis done as part of the support case).

Please note that this is a full release of Connect, not a patch or service pack.
In line with OpenText versioning policy, the last tuple ".1" indicates that this is the second release of Connect within the first quarter of calendar year 2024.