Possibility of Recalculating delay time for Messages on Add activity trigger

Hi Team,

We have a requirement to send reminder emails to dispatchers if an activity remains unaccepted 20 minutes after its creation. Since our technicians do not use the OFS mobile app, we rely on a custom property sent from an external mobile application to track acceptance.

To implement this, we created a message scenario triggered by the "Add Activity" event with a 20-minute sending delay. We also included a blocking condition to check whether the activity has been accepted. However, this approach fails when the activity is moved to a different field employee or bucket, as the "Add Activity" trigger is re-initiated on Move, and the 20-minute delay is recalculated from the latest move time rather than the original creation time.