Arch Linux

Our current nextcloud-cron.service misses the KillMode directive
https://github.com/archlinux/svntogit-community/blob/packages/nextcloud/trunk/nextcloud-cron.service

Check Nexcloud documentation: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html#systemd
"The KillMode=process setting is necessary for external programs that are started by the cron job to keep running after the cron job has finished."

This should prevent unwanted data loss or memory corruption or even memory leaks.

But I suggest to follow https://www.freedesktop.org/software/systemd/man/systemd.kill.html upstream recommendation and prefer
"KillMode=mixed"
"If set to mixed, the SIGTERM signal (see below) is sent to the main process while the subsequent SIGKILL signal (see below) is sent to all remaining processes of the unit's control group. If set to process, only the main process itself is killed (not recommended!). If set to none, no process is killed (strongly recommended against!). In this case, only the stop command will be executed on unit stop, but no process will be killed otherwise. Processes remaining alive after stop are left in their control group and the control group continues to exist after stop unless empty."

I'm not sure if using "control-group" mode could even be better. But this would probably need some additional ExecStop= command.