Bidirectional issue in ServiceNow ebonding

[User205031]

Hi All,

I'm facing one issue.  We are doing bidirectional eBonding between two instances to copy incident records using flow designer and "ServiceNow remote instance spoke" and created flows on both the instances.

However, the issue is it is going in endless loop and executing the flows on both side continuously. The trigger condition on instance A is Impact is High. When we are creating incident on A instance the flow on A instance gets triggered and incident gets created on instance B. So likewise continuously it is executing flows on both the instances and multiple incidents are getting created on both instances and correlation id and incident numbers are different from each other. . How can we solve this issue?

Thanks!

[Tony Chatfield1]

Hi, normally in an integration I would add a trigger condition of
sys_updated_by ISNOT yourIntegrationAccount.
I suspect you are seeing the results of not including this so something changes and an integration message is triggered, as a result something changes and an integration message is triggered ...

[User205031]

Hi Tony,

I created one Basic Auth credential and one connection for this eBonding. So my question is which is the integration account you are referring to? Is it my Basic Auth credential?

Thanks!

[Tony Chatfield1]

Hi, this is the account that is used to process the records in your instance,
and so it would normally be the user whose credentials are used to authenticate you to the instance.
If in doubt check the sys_updated_by field for records that are inserted\updated by integration,
this field will show the user id of the account involved.

[User205031]

Hi Tony,

The issue is fixed by updating the trigger condition. I have added correlation id is empty for  the flows both in source and target instance. Now, only one incident is getting created.

Thanks!