Added a retry flag to the Halo sync log.
product review
Kevin French
Due to rate limiting issues with Halo, we’ve implemented a retry mechanism for certain APIs to help ensure data integrity for our clients.
However, clients are currently unable to see from the logs whether these exceptions have already been retried successfully. As a result, they still see the error messages and cannot disregard them with confidence.
To improve clarity, we’d like to request either a clear indicator showing that a retry was successful, or that the error message be cleared automatically after a successful retry.
Log In
Micus
Merged in a post:
Misleading on the Halo synchronization details page.
L
Leon Black
Root Cause:
Although there is an exception displayed in the detail, there is a retry mechanism in the synchronization system, so it does not affect the final result of the data.
Solution:
Contact the customer to inquire about the specific dataset name.
Then investigate what exactly is wrong with the data.
Impact: Data synchronization.
Check list:
Will this issue reoccur for this tenant? No
Will this issue occur for other tenants? Yes
Will other modules within this integration face similar issues? Need to investigate
Will other integrations encounter this issue? Need to investigate
Is this issue completely resolved? No
The customer does not understand the synchronization logic, so when the customer sees an error through the details page, they think it is a real error.
Please confirm the product: whether it is possible to avoid customer doubts from the perspective of design.
Next Steps:
Communicate with customers.
Investigator: Jerry Sun
Micus
product review