On the latest v3-30 plugin and this morning's parity check did not pause. Furthermore, if I try to set a different time for the pause while the parity check is running, 95% of the time the changes don't stick when hitting "apply". (i.e. changing the pause and resume times). I can toggle the scheduled check to yes or no, but the times usually don't change. I also tried reinstalling the plugin but the same behavior was exhibited. I'm on unraid 6.9.1.
EDIT: Changing increment frequency to custom and changing the pause/resume times with crontab format work, but I can't enable sending notifications for pause or resume of increments. Strange. I guess we'll see if it pauses at half past the hour, but it didnt at the top of the hour previously.
EDIT 2: No joy. 30 7 * * * pause time had no affect and the parity check continues. Nothing in the log.
EDIT 3: Changed the log level to testing (derp. Should have done that to begin with when I discovered it didn't work). Looks like the plugin thinks I kicked off a manual parity check, when it's actually a scheduled one:
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: ----------- PAUSE begin ------
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: DEBUG: Pause request
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: /boot/config/forcesync marker file present
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: progress marker file present
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: manual marker file present
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: disks marker file present
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: ... appears to be manual parity check
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: ...configured action for MANUAL Correcting Parity Check: 0
Apr 1 07:37:01 ADRASTEA Parity Check Tuning: TESTING: ----------- PAUSE end ------
EDIT 4: Set "Use Increments for manual parity check" to "Yes" (for testing. Would prefer this to be off regularly) and it paused at the next scheduled time ( I set it to 40 7 * * * ). So, it pauses, but I guess it thought my scheduled check was manual somehow. That seems to be the conclusion of my report.