We have noticed one issue when the phone is turned off or dies. When it is turned back on, we are getting multiple audible and haptic alerts (and asked to complete the last missed medprompt), and then need to manually fire the triggers in order to receive any new prompts/EMAs.
The basic problem sequence is:
Device powered off.
Trigger(s) that would run, cannot, because the device is powered off.
Device power on.
PR runs the triggers that would have run in step 2.
Step 4 in that sequence is the issue.
Discussed solution: Add a flag to triggers that allows the developer/user to prevent this. The trigger runner would, for a trigger to be run, check whether it was supposed to run at a time occurring prior to the device's start time, and if the flag state disables execution, then the trigger does not run (else, it runs).
From a customer:
The basic problem sequence is:
Step 4 in that sequence is the issue.
Discussed solution: Add a flag to triggers that allows the developer/user to prevent this. The trigger runner would, for a trigger to be run, check whether it was supposed to run at a time occurring prior to the device's start time, and if the flag state disables execution, then the trigger does not run (else, it runs).