I have built a safety app that allows users to notify ‘an authority’ they are heading out , where they are going and when they are due back and once back the user closes down their journey. If they are not back by their due back time.
i have multiple pairs of tasks that run during the day and email anyone who has indicated they have not returned and it is past their due back time. The second task in the pair runs 2 mins later and changes a record to notified, so when the pair of tasks run again they don’t get a second email.
This has been running well for a week, but today the first tas has run 20 mins late, but the second task ran on time, which meant no one got emailed as the second task changed the flag to notified. This resulted in multiple escalations of the emergency services for non returned people, who just hadn’t been reminded to close down their journey logs.
Can tasks be relied upon with Knack to run on time? Is this delay a one off or a regular occurrence?
It seems crazy if there is known unreliability of tasks to run on time, that you cannot carry out multi-stage tasks as a change state after email sent is pretty much a given for any task-based automation.