Mover logging and exit status codes

If I enable mover logging I get syslog entries like this:

May  4 03:00:01 Lapulapu root: mover: started
May  4 03:00:01 Lapulapu move: move: file /mnt/cache/L_Public/Plex Media/TV Recordings/The Stuarts A Bloody Reign (2018)/Season 01/The Stuarts A Bloody Reign (2018) - S01E02 - Episode 2.ts
May  4 03:00:33 Lapulapu move: move: file /mnt/cache/L_Public/Plex Media/Movie Recordings/Flight of the Phoenix (2004)/Flight of the Phoenix (2004).ts
May  4 03:01:11 Lapulapu move: move: file /mnt/cache/L_Public/Plex Media/Movie Recordings/The Girl With the Dragon Tattoo (2011)/The Girl With the Dragon Tattoo (2011).ts
May  4 03:01:29 Lapulapu root: mover: finished

as you might expect. But if I disable mover logging I get this instead:

May  1 03:01:38 Lapulapu crond[1585]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null

which has me puzzled. Non-zero exit codes conventionally indicate a failure. A brief inspection of the /usr/local/sbin/mover script suggests that exit code 1 means "mover: already running":

start() {
  if [ -f $PIDFILE ]; then
    if ps h $(cat $PIDFILE) | grep mover ; then
        echo "mover: already running"
        exit 1
    fi
  fi

Or is it crond that's returning exit code 1? I don't think this is specific to unRAID 6.5.1. It's just that the advice these days is to disable mover logging. Can anyone explain, please?