View the original community article here
Last tested: May 25, 2020
This error may come up in existing schedules that "worked" fine due to scheduling permissions changing from instance wide to model specific in 6.24.
The biggest post 6.24 change is that yeah, for system_activity the schedule owner has to be an admin because schedule content is on the model level and system activity cannot be added on a model set level.
This content is subject to limited support.