Currently it is defined that the user running CRON is forced to be anonymous but this may not be correct in cases, such as having a headless head with the content access API capped, which causes constant access errors every time CRON is run.
My proposal is to make configurable the user with which CRON is executed by modifying the SimpleCron file in charge of overwriting the system CRON.
Yes, in the configuration section of simple_cron you should be able to select the user with which CRON will be executed, so we have available all the roles/permissions layer for this.
N/A
Yes, we should be able to store the selected user.
Active
1.0
Code
Perhaps the configuration form could have a selection based on role or select a particular user. Based on role the problem is the code would create then clean up a user, so user IDs would increment. Based on user the problem is user could get deleted (though I suppose it could fallback to status quo if that happens).