I’ve been running into an issue lately where my scheduled work plans (I have one for the front yard and one for the back yard) aren’t running. When I check the Work Plan History in the app it shows that the work was completed but only took a few minutes. The clean area shows the full 16k sq ft as being mowed. If I run the work plan manually it runs fine.
Initially I thought it was just an issue with the Front Yard work plan or schedule as it only affected that one but now both plans are having the same problem.
I have a ticket in with support and they’ve escalated it but its been a few days and the problem still exists (I’m sure they’re a bit swamped with the security updates and firmware patches) so I figured I could post here and see if anyone else has dealt with this issue and might know of a solution.
Hi there, I’m really sorry for the inconvenience caused. I’ve checked your support ticket in our system, and thank you so much for your patience while our team continues investigating the issue.
We understand how frustrating it is when scheduled work plans are not running correctly, especially when manual runs are working normally. Your case has already been escalated, and our team is still actively looking into it. We truly appreciate your understanding and patience in the meantime.
Received an update on the ticket. It’s a known bug that should be fixed in a later firmware release. Current work-around is to edit the work plan and save again (no changes are actually needed). I guess what is happening is that the plan is starting at 99% completion (which makes sense and not something I would have caught normally).
Tried it last night and the plan ran correctly this morning!
I’m experiencing this same thing, but when I manually kick off the work plan it works. Is the suggestion to edit the plan and just hit the save checkmark?
It is amazing the amount of issues these updates create. Maybe Yarbo needs to expand the PPP team to get more testing done if they can’t do it in house.
We got them first during the phased rollout. In theory hotfixes shouldn’t need extensive formal testing because they are small corrections for bug fixes. Streamlined testing should be sufficient. But if the changes are somewhat risky or extensive, then they should be extensively tested.
Unfortunately the problem came right back again a couple days later. I think I know what the culprit is though. I had the schedule set to “Resume Next Time” and my theory is that even though the job finished completely it only logged it at 99% internally. I’ve set to to “Start over next time” and will see what happens next week…
It shows as “Completed” with 100% Progress. 16,000 Sq Ft mowed in 7 minutes doesn’t seem that feasible. (But would be an amazing selling point if it could do it!)
