[Backend Bug Report] Quest instance not finished on-complete triggered and device moved to new instance. about realdevicemap HOT 7 CLOSED

[2020-05-02 15:56:08 GMT-05:00] [DEBUG] no job left (Got result: ["status": ok, "data": { [2020-05-02 15:56:08 GMT-05:00] }]

from realdevicemap.

Are the stops closed?

from realdevicemap.

Same experience here, large area never finishes. Stops are not closed. Reassigning a device back does not work.

Done: 16112|16125/16125 (99.9|100.0%)

from realdevicemap.

@jepke @tppkgo are those stops closed at night?

from realdevicemap.

The ones in my screenshot actually are i found out later but in this same run i had other small clusters and single stops that had been skipped as well and those are not closed night time.
But as you mentioned on discord it might be the 3 mis skip function causing this. As most of the time the ones not being done are in rural areas.

In my case reassigning a device to finish leftovers works but depends on how many are left over i might have to reassign a few times to hit 100%

from realdevicemap.

Just had 1 tiny instance 371 stops stuck at 361 (route 100%) changed login delay to 86400 and it finished the last 10 in a minute after changing. Don't know if the instance edit triggered something or the login delay.

A 154 instance stuck at 153 reassigning kept moving the device to the on complete instance right away changed the name of the instance reassigned a phone and did the last stop. So i would say the 3 mis skip function.

from realdevicemap.

Potentially fixed in #122
Re-open if this is still an issue.

from realdevicemap.