Manjaro doesn’t encourage the use of cron but the use of systemd timers.
A timer activates a service definition on a schedule.
The service definition and timer definition mandates same name but different extension
~/.config/systemd/user/ssh-test.service
[Unit]
Description=Run ssh connection test
# wait for network
After=syslog.target network.target default.target
[Service]
Type=simple
ExecStartPre=/bin/sleep 30
ExecStart=/home/%u/ssh-test/ssh-test2.sh
[Install]
WantedBy=default.target
~/.config/systemd/user/ssh-test.timer
[Unit]
Description=Schedule ssh test
[Timer]
OnBootSec=10m
Persistent=true
OnCalendar=0/1:00:00
OnUnitActiveSec=1h
[Install]
WantedBy=timers.target
Enable and start only the timer as the timer will activate the service which runs the script
systemctl --user enable ssh-test.timer
systemctl --user start ssh-test.timer
A point to consider in your script is your output files. Depending on the path from where the script is run the files will be created in arbitrary locations.
So defining your output files with a full path will ensure they are always created/modified in the same location
[...]
output_files=( "$HOME/server1_output.txt" "$HOME/server2_output.txt" )
[...]