At present with the mower, if there is a bumper strike or other obstruction, the core will retry the dead end several times. If it cannot clear it, it stops the entire plan.
This often occurs to me on steeper hillsides where the orientation of the core is critical. If the grass is wetter, or dryer, or different than when the dead-end was created, the core will crab/slide differently during the climb or descent and collide with things that it previously didn’t when mapped, or even the day prior. Next week, the grass will be different and the dead-end will succeed. Once that hillside dries out, it’ll fail again. Or, perhaps there are actual objects blocking the dead-end, for whatever reason. It doesn’t really matter, the entire plan is stalled for something that cannot be resolved without editing the plan to remove that Dead End.
Since there are serious cases that need the “pause” behavior to remain, an option to “Consider Dead-End complete if obstructed” would be ideal, instead of pausing. If the core cannot complete it, fine. Log the error and move along to the next.
I’ll argue for making it a per-dead-end setting, or perhaps a plan setting. It should not be a global preference.
The way the core/M1 climbs / descends a hill involves crabbing. On the climb, the M1 will crab uphill, with the core in the lane and the M1 above it. On the decent, the M1 will crab downward, below the lane. The steeper the hill, the more outside the lane the M1 will be. And as traction is reduced, the crabbing increases.
As a DE is created, the user might have a downhill obstruction, tree, wall, whatever, that is cleared during creation - but if the grass is wet, or mud, the M1 will strike it during descent. The user might need the Pause to occur on that specific DE, if a strike occurs during reverse. The same is true if a DE occurs along a basement wall, even on flat ground; if a strike occurs during reverse, the user will probably want the core to stop instead of climbing and destroying itself.
There are other cases where a bumper strike in reverse is not a big deal. Trees and fence posts, for example - the M1 can just bounce off and keep backing down the DE, without pausing the plan, and certainly without retrying the Dead End.
The same holds true when climbing forward; generally, a bumper strike can simply end the Dead End, and the plan moves on. Dead-ends that end facing against a wall or post, for example.
That said, with the option enabled if the core slides out of the DE’s lane and is not in an area, the plan should pause. If the core slides out of the DE’s lane and it remains in an area, the DE should be considered complete and the error should be logged.
This new option would be “pause” by default, whereever it ends up.
Cheers,