Reproduced In Native (app.bringg): Yes
Problem: When navigating to the dispatch list we are seeing both canceled and completed DoorDash orders making their way into the dispatch list from the open tasks endpoint above. This is not limited to only DoorDash and appears to occur with third party orders.
I'm noticing that the status property has remained unchanged in these orders displaying as status: 0 which may be how it is making it through in the first place.
Is this a known issue and are there any properties coming back from that enpoint I may be able to leverage to filter out cancelled/completed orders? I see when I remove the parameters appended on the endpoint I gain access to cancelled_at which may suffice as a short term solution for cancelled orders, but I'm trying to identify what field I can utilize for a completed order that has made it in through this enpoint. Any ideas on a quick fix for the time being?
Please sign in to leave a comment.