Q: How can I retrigger a task?
Once a task has been initiated, users can trigger it again at any time. For example: a user created a trip sheet, and later the itinerary for that trip is updated. Retrigger the task to generate a new trip sheet that reflects the most up-to-date information in Qargo.
Retrigger a task on stop level
Documents created on stop level show on the consignment itself. To retrigger the document generation, go to the Stops documents and tasks section of the Execution.
Find and expand the stops.
Click +tasks to expand tasks that have already executed.
Locate the tasks available for those stops. The option to retrigger is shown there.
Bulk actions on failed tasks
When many tasks have failed at once, for example after an integration issue or a bulk import error, the Failed Tasks page supports bulk Re-trigger, Reset and Skip in a single operation.
How to open the Failed Tasks page
Click the action button in the top right corner of the navigation bar. It shows a red notification badge when there are failed or in-progress tasks.
In the dropdown that opens, click the eye icon next to failed tasks.
The Failed Tasks page opens.
How to retrigger in bulk
Select the checkbox for all the tasks to retrigger.
Click Re-trigger.
Q: When do we retrigger a dispatch?
This section gives an overview of what happens when information on a trip is updated, who is informed and how.
Q. If my trip is dispatched and something is updated, like a telephone number or a reference, how is the information updated?
A. Most trips today have some element of integration with other services, customers and communication systems. Information flows constantly between these parties and is typically "set" at the point of dispatch. Many data points, for instance a customer reference number or a contact telephone number, are used by other functions and by any of the parties in the order.
When information is updated in Qargo, a Redispatch is triggered that includes the updated information.
Redispatch is an automatic update that happens when these fields are changed, unless the load is completed. For completed loads, these do not update.
Redispatch triggers: STOP update
All updates below are sent to FMS / Mobile App / Pallet Networks.
Update performed
Date
Estimated Start
Actual Start
Actual End
Location
Any field related to 'Addon'
Note
Reference Number
Any additional field linked to stops
Stop Type
Skip Dispatch
Phone number
Mobile number
CMR Reference Number
Any additional field linked to Consignee
ECMR
Redispatch triggers: CONSIGNMENT update
All updates below are sent to Container / Intermodal Booking.
Update performed
Description
Quantity
Total Weight
Total Volume
Weight unit of measurement
Volume unit of measurement
Any additional field linked to goods
Total Loading Meters
Total Pallet Spaces
Packaging
Commodity Name
Actual Loaded Quantity
Actual Total Weight
Minimum Temperature
Maximum Temperature
specific_gravity
Any field related to Add-ons
Redispatch triggers: ORDER update
All updates below are sent to FMS / Mobile App / Pallet Network.
Update performed
CMR Reference Number
Container Number
Customer Reference Number
Any additional field linked to orders
Name
Any field related to Add-ons
Redispatch triggers: CONTAINER / INTERMODAL BOOKING update
Update performed | Redispatch / update sent to |
Most changes in information on the Container Handling / Container Booking / Intermodal Booking | FMS / Mobile App / Pallet Network, Container / Intermodal booking dispatch, Container handling dispatch |