@carl We did have a breaking update quite a while ago with an update and it looked something like this. The ‘work around’ was to delete the scheduled snapshot task and re-create it. It was unfortunate and we had to make some pretty deep changes on a design level that made some breakage difficult to avoid.
Git that a go and do mention if this did not coincide with an update as that would make it more likely to be an as yet unknow bug. But we haven’t had any reports of this that can’t be explained by an update (at least yet).
Hope that helps.
Incidentally the low level move we made was to transition our share / pools over from name to number and hence the breakage in scheduled snapshot tasks that previously referenced name and then expected a number.
This looks to be related, although strangely the other way around. Try deleting the scheduled task and re-creating and report back on your findings.
Linking to your prior scheduled (scrub in this case) task which is the only other recent report of scheduled tasks issues. I’m guessing these tasks were both created in an earlier version of Rockstor and both suffered from this API change we had to make. Bit of a rocky time it was but we had to do it as many other problems were sorted by that change but unfortunately we failed to catch all of them in their scheduled tasks knock on.
Hope that helps and thanks for helping to support Rockstor’s development via a Stable channel subscription.