Call API endpoints asynchronously

[dmitriim]

At some point API end points could be slow. This will slow down Moodle operations related to the configured events.
The solution could be to have a configuration option to run web hooks asynchronously via adhoc tasks or cron task.

[valentineus]

Thanks! It's a valuable issue.

I too see this problem. This problem will be to resolve a new version. I'm using adhoc_task to asynchrony work.

[dmitriim]

Nice!
Would it be possible to make it configurable and let the admin to decide if a webhook should be processed real time or by adhoc?
Also would be useful to fall back to adhoc if for some reason the webhook failed during real-time execution.

[mlohoar]

I agree that this should definitely be a setting for using adhoc or not. Otherwise you might get into race conditions between Moodle and the external service.

[vtos]

My point is it must always be a background task, I mean making those calls. The event handler should just make up a queue of those API calls and store it, and a worker should be running to make the calls actually. This will also allow for having a retry flow in case an API call failed (which is super-highly possible).