-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Speed of enrolment? #17
Comments
The enrollment by course completion happens when the course_completed event is triggered. This is not instantly, but very fast: triggered events are queued in FIFO buffer and are processed only after all observers of the event are notified. This plugin is only using the the good old Moodle cron job to send welcome emails: these messages are not sent immediately but generated during an adhoc task. Adhoc tasks do not run out of the blue, but start because cron tells them to do so. |
But I thin course_completed is triggered in (some?) cases only by a cron on Moodle 3.9 ? |
Indeed, that is sth we realized, too. So we had to trigger cron more frequently to reduce the time until the enrollment completes. And added a note to the users, to wait a few minutes and try again. |
Sometimes the cron needs to be executed even twice. In another task we wrote this to enforce the completion calculation
|
Did you ever try to create an additional cron task running every minute with this as content:
|
MDL-32103 made course completion instant for activity based completion criteria. Other criteria still need 2 cron jobs. So there is a significant change in the speed of the enrolment when using activity based completion criteria. |
As I understand, the enrolment checks via event observation for course completion, not as a cron job, thus it should happen rather instantly? Or is it still reliant on some general Moodle cronjob?
The text was updated successfully, but these errors were encountered: