Out with the old and in with the new!
As you may have heard, we are currently rolling out a new architecture at Stuart! 
All being well this rollout should be complete in all of our operating countries and cities by October.
This migration was designed to be transparent with no impact to our service and no changes required from our integrators. Nevertheless we would like to take this opportunity to notify you all on two notable changes that you may notice:
Fewer ID changes and cancellations 
There are several reasons why our support may need to reassign a new driver to a job.
In our old architecture reassigning a driver meant voiding or cancelling the job to create another. This meant receiving a cancelled status and new job and delivery IDs would then be used as the order continues it’s life cycle.
In our new architecture we have pickup and dropoff tasks which can fail or succeed. Our support will be able to create new tasks rather than new jobs, meaning that the IDs don’t change and there is no cancelled status relating to driver reassignments.
Summary: In the new architecture when a driver is reassigned you will not receive a cancelled status or new job and delivery IDs.
New possibilities for expirations 
Both our previous and new architecture allow for a set expiration interval to be setup for a clients account, more detail on this topic can be found here. Once the time a job has been searching for a driver reaches the custom expiration interval the job expires with the ‘expired’ status.
In our old architecture if there is no expiration interval setup a job will search for a driver based on zone expiration intervals, after which time the job expires. In our new architecture however, reaching this zone expiration interval will not result in an expired job. Instead our support will be able to relaunch the job at anytime in that days operational hours, with the ‘expired’ status only being received at the end of these operational hours if a driver cannot be assigned.
This gives us the opportunity to fulfil job requests without the need to send a new job request after an initial expiration. This change will be particularly useful to clients offering same day delivery.
Please note: if you do not have an expiration interval set up in your account jobs might not expire until the end of the day. Please see our dedicated article on change to expirations for more information on this change.