Service Exchange - Some inbound records are taking abnormally long to process finding threshold

MattCD
Tera Contributor

We are receiving repeated issues/notifications related to Service Exchange for the instance scan "[PRO][CON] Transport inbound queue processing is slow" titled "Some inbound records are taking abnormally long to process".  These are always flagged as P1.

 

However, we get these notifications for almost any record that has an attachment. Per the recommendation we have increased the glide.hub.process.sync.jobs.inbound.subflow.execution_timeout, however the scan will always report an issue because it has hard coded SLOW_MICROSECS to 20 seconds. To make matters more challenging the scan has a read only protection policy so we cannot modify it to prevent these notifications from repeatedly triggering.

 

My 2 cents
1. The default scan value of 20 seconds is too low and will produce many false positive issues
2. The protection policy on the scan is read only so we can't turn this off or at the very least, set to a P2 or lower finding.

 

@Kenny Caldwell Is there any known solution internally to this?

0 REPLIES 0