The docs state that the ‘returning’ status may not be triggered in all cases…how do I mitigate for this. It’s paramount that I am able to code for this…the testing scenario found at https://dashboard.sandbox.stuart.com/ has worked one time but the webhook is not triggered in subsequent cases
Thanks
Hello @lmitchsmith,
In our documentation, returns are marked as optional because some clients don’t require couriers to return to the store in the event of an unsuccessful delivery. For example, restaurants might prefer that the courier dispose of the package instead.
Regarding the issue you’re facing, there is a bug in the sandbox that prevents deliveries from being completed. This bug has been reported internally. I’ll update you next week on the progress of the resolution. In the meantime, we have manually completed your deliveries so that you can receive the webhook events.
Additionally, could you provide us with more details about how you are integrating our API?
What system will be connected to our API?
This will help us better understand your needs and provide more tailored advice.
Thank you in advance.
Please keep me notified…I noticed today that upon testing the return path scenario it seems to be ignored in favour of delivering the package to the destination when in fact I would wish it returned to the pickup… To answer you questions we are a website with Node JS backend nothing too complicated
Hello,
Do you know if the ‘return’ scenario was active from the time the package was created until the delivery was completed?
More generally, for the scenario you are testing to work correctly, you must ensure it is active the entire time.
I also sent you a private message because I still have a few questions.
Thanks