Optimized Event Generation for Indirect Activity Updates

With the 25D update, an enhancement is introduced to improve system performance by reducing the number of unnecessary activityUpdated events that are triggered during route recalculations. This change specifically applies to activities that are not directly modified but whose estimated start times change because of updates to other activities in the same route.


Consider a situation where a dispatcher mistakenly assigns an excessive number of activities to a technician’s route. If one activity is delayed or rescheduled, the system automatically recalculates the route and adjusts the estimated start times for all affected activities. Previously, each of those activities would generate an 'activityUpdated' event, even for activities where the recalculated estimated start time falls several days after the activity’s scheduled date. This led to excessive and often redundant API traffic and event handling.


With this new enhancement, the system suppresses 'activityUpdated' events for activities that meet both of the following conditions:

  • The update is indirect, meaning it is not triggered by a direct user or system change to the activity itself, but rather results from a change elsewhere in the route. For example, when a new activity is added to or removed from the route, or when the Duration of a previous activity is changed.
  • The activity's new estimated start time falls 48 hours or more after the activity's scheduled date, based on the time zone of the assigned resource.

By suppressing these low value events, the system maintains critical updates while eliminating unnecessary noise.

Business Benefit

  • In case when too many activities are put into a resource route, e.g., by a mistake, the system will spend less resources for processing changes in that route, Integrations will receive less of unnecessary API traffic.
  • Improves system performance and stability by reducing the number of unnecessary activityUpdated events when activities are indirectly affected by route changes.
  • Minimize API traffic with integrations, lowers processing load, and ensures that only meaningful updates are communicated. As a result, systems that consume these events such as real-time monitoring tools remain focused and efficient.

Steps to Enable

This functionality is available with 25D and doesn't require actions to enable it.

Tips And Considerations

  • This feature only affects activityUpdated events that are generated indirectly during route recalculation. If an activity is updated directly for example, by a user or using API the activityUpdated event is still generated, regardless of how far in the future the activity is scheduled.
  • The 48-hour threshold is calculated based on the activity’s original scheduled date + 48 hours, using the time zone of the assigned field resource. If the new ETA falls on or after this threshold, and the update is indirect, the event is not generated.