ver 0.1 (0.10)

Package Link: Click here.

This release enhances system performance and user control by preventing overlapping historical syncs and introducing an intelligent retry mechanism that reprocesses only failed records. To improve reliability in error recovery, historical syncs will now automatically retry after encountering rate limit errors. Additionally, the release delivers UI improvements, such as clickable Record ID hyperlinks for easier navigation and the ability for admins to delete exception records.

What's new?

(UI Update) Historical Sync Behaviour

To prevent conflicts and improve sync reliability, a restriction is now in place:

Only one historical sync can be initiated at a time per workspace/connection for MoEngage User and Event objects. While a sync is in progress (unless it completes, fails, or partially succeeds), all other syncs for the same MoEngage object will have the 'Sync' button disabled.

Example: If a historical sync is started for the MoEngage User object, then other syncs for the MoEngage User will be disabled. However, syncs for the MoEngage Event object will remain available.

(UI Update) Record ID hyperlink

To enhance accessibility to the underlying records for which Sync Queues and Exceptions are created:

  • Provided the ‘Record Id’ in the ‘All’ list view of the Exception object and on the record detail page, allowing redirection to the record against which the Exception was raised.
  • Provided the ‘Record Id’ as a hyperlink in the ‘Real-Time Syncs’ list view of the Sync Queue object and on the record detail page, enabling redirection to the record for which the Sync Queue was created.

(UI Update) Delete functionality on Exception Records

Allow admin user to delete Exception Records:

  • Provided a standard Salesforce Delete button on Exception records.

Process Improvements

Rate Limit Recovery

Historical syncs that encounter a "Rate Limit Exceeded" error will now automatically retry, with the retry attempt count reset to 0.

Smarter Retry Logic

Historical sync retries will now only reprocess failed records, significantly reducing redundant operations and improving efficiency. This applies to the following error types:

  • Account Suspended
  • Authentication Required
  • BlockedClient
  • Rate Limits Exceeded
  • Server Error
  • Unsupported Media Type

Package Upgrade Behavior for List View & Page Layout changes

List View Behaviour

List views are not auto-updated when the package is upgraded. Users need to manually update the list views to include the ‘Record ID’ field. List Views that need update:

  • All – List view present on the Exception object
  • Real Time Syncs – List view present on the Sync Queue object

Page Layouts Behaviour

Page Layouts are not auto-updated when the package is upgraded. Users need to manually update the page layouts to include the ‘Record ID’ field & remove the earlier ‘Record ID’ (Text) field if present on the layout. Page Layouts that need updating:

  • Exception Layout – Page Layout for Exception object
  • Historical Sync Layout – Page Layout for Sync Queue object (Along with Record ID Update, also add ‘Record ID’ hyperlink field in ‘Failed Sync Queues’ Related list.)
  • Sync Queue Layout – Page Layout for Sync Queue object

 

 

Previous

Next

Was this article helpful?
0 out of 0 found this helpful

How can we improve this article?