I'm using NINA and got that a couple of times, had to restart the model.
The floating-point divide error is displayed being displayed by ASTAP. I've seen ASTAP do this occasionally during testing, but it wasn't consistent. Unless it is often happening, you shouldn't need to start over. APPM will move on to the next point.
Not sure why that happens.Only the ASTAP developer would be able to fix this issue. If you set APPM to save failed images, they could be posted to the ASTAP support forum for the author to inspect.