Current behavior on sandbox:
processing
, set drivers not availableno_drivers_available
as expectedprocessing
I would be expecting the request to not go back to processing
and rather stay on no_drivers_available
. Is this a bug or is that your defined behavior? If so, could you provide more explanation?
If there is valid ride request with "processing" status - and product that was used to create this request was modified and set drivers_available to false, ride requests will terminate with the status "no_drivers_available". If product gets modified again and set drivers_available to true - ride request status will change to "processing" again - and closest available driver will be able to accept this request. So there is no "bug" in this flow - and this is expected behavior.