As a Builder I want to be able to link my tasks so that I can be certain that the tasks run in the correct sequence.
Daily Task 1 [1/2] - Updates records in a connected table/object or sends en email
Daily Task 2 [2/2] - Updates the record to indicate that it is done and does not have to be repeated
As of today I have postfixed the labels of my tasks [1/2] and [2/2] (as above) and made them run with a several hours time difference. However I am still getting issues (for task concurrency reasons ) that Task 2 sometimes runs before Task 1. This will mean that the whole operation is marked as done, even though it isn’t.
For the same reasons it sometimes happens that Task 1 is completely skipped for a whole day (because of task concurrency limits on the server and high utilization of tasks in same or other apps or even other customers apps). Typically this can happen in the end or middle of months. This also can result in the operation marked as done even though Task 1 is never run.
The last scenario is that if there is a long timespan between Task 1 and Task 2, the users can change the data both tasks use as a select criteria. This can also result in Task 2 triggering before Task 1. Again this will lead to the operation marked as done even though Task 1 has never run.
This is a data consistency issue as long as we can’t trust the tasks running exactly on the scheduled time. Even though we could, the idea of linked tasks (task dependency) would be a safer and cleaner way of implementing slightly more complex tasks.