Good afternoon, I was doing some more tests, the attendance is limited to task-adhoc.
what happens is that when the ad-hoc stack mainly sends mail, when cron runs the next time they start executing the same tasks on the stack simultaneously. if the delay is even longer and the cron runs very frequently, many ad-hoc can be executed simultaneously.
the problem is not the simultaneity but the concurrence on the same tasks.
The same ID from the mdl_task_adhoc table is executed for each cron generating duplicate submissions.
create a Moodle Tracker: https://tracker.moodle.org/browse/MDL-69725
what happens is that when the ad-hoc stack mainly sends mail, when cron runs the next time they start executing the same tasks on the stack simultaneously. if the delay is even longer and the cron runs very frequently, many ad-hoc can be executed simultaneously.
the problem is not the simultaneity but the concurrence on the same tasks.
The same ID from the mdl_task_adhoc table is executed for each cron generating duplicate submissions.
create a Moodle Tracker: https://tracker.moodle.org/browse/MDL-69725