---
title: "FAQ – Retrigger tasks and dispatches"
description: "How to retrigger a task (for example, to regenerate a document), and when Qargo automatically retriggers a dispatch when information changes."
url: https://help.qargo.com/us/articles/160700-faq-retrigger-tasks-and-dispatches
locale: us
updated: 2026-10-21
---

# FAQ – Retrigger tasks and dispatches

## Q: How can a task be retriggered? {#h_bddb925ab0}

Once a task has been initiated, users can trigger it again at any time. For example, a user created a load sheet, and later the itinerary for that load is updated. Retrigger the task to generate a new load sheet that reflects the most up-to-date information in Qargo.

::video{src="/media/video/5d49b3ea6694-CleanShot-2024-04-26-at-13_10_05.mp4"}

### Retrigger a task at stop level {#h_5b67da31b9}

**Documents created at stop level** show on the shipment itself. To retrigger the document generation, go to the **Stops documents and tasks** section of **Operations**.

1.  Find and expand the stops.
2.  Click **+tasks** to expand tasks that have already been executed.
3.  Locate the tasks available for those stops. The option to retrigger is shown there.

    ::video{src="/media/video/e270b1f7c344-2024-07-02-12_06_33.mp4"}


### Bulk actions on failed tasks {#h_f705b64236}

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.

![](https://help.qargo.com/media/43c00085e2e1-image.png)

**How to open the Failed Tasks page**

1.  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.
2.  In the dropdown that opens, click the **eye icon** next to failed tasks.
3.  The Failed Tasks page opens.

**How to retrigger in bulk**

1.  Select the checkbox for all the tasks to retrigger.
2.  Click **Re-trigger**.

    ![](https://help.qargo.com/media/9db575b84ea2-image.png)


## Q: When is a dispatch retriggered? {#h_d80b513e0b}

This section gives an overview of what happens when information on a load is updated, who is informed and how.

**Q. If a load is dispatched and something is updated, such as a phone number or a reference, how is the information updated?**

**_A._** Most loads 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, such as a customer reference number or a contact phone 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._**

:::callout{tone="note"}
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 {#h_d84cb957c6}

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

* * *

Cell number

* * *

Email

* * *

CMR reference number

* * *

Any additional field linked to receiver

* * *

eCMR

* * *

### Redispatch triggers: shipment update {#h_923edc30dc}

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 {#h_500c6ecd5a}

All updates below are sent to **FMS / Mobile app / Pallet network**.

Update performed

* * *

CMR reference number

* * *

Container no.

* * *

Customer reference number

* * *

Any additional field linked to orders

* * *

Name

* * *

Any field related to add-ons

* * *

### Redispatch triggers: container / intermodal booking update {#h_01b2949be1}

| 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 |


## Related articles

- [Changes to loads that have been sent to drivers](https://help.qargo.com/us/articles/133786-changes-to-loads-that-have-been-sent-to-drivers.md)
- [Tasks – Complete tasks in bulk](https://help.qargo.com/us/articles/133829-tasks-complete-tasks-in-bulk.md)
- [FAQ: Why are document changes not visible?](https://help.qargo.com/us/articles/421960-faq-why-are-document-changes-not-visible.md)
- [FAQ: How to add questions in the Qargo driver mobile app](https://help.qargo.com/us/articles/421743-faq-how-to-add-questions-in-the-qargo-driver-mobile-app.md)
- [Tasks: troubleshooting tasks](https://help.qargo.com/us/articles/431269-tasks-troubleshooting-tasks.md)
