Carrier health
What this is
Carrier health shows whether each connected FedEx and UPS account is actually delivering tracking numbers. It lists every supply partner and carrier with a coloured status, counts recent messages and failures, and lists what the nightly check found missing. Open it after connecting a carrier, and whenever the office says tracking numbers have stopped appearing on their own.
The shared demo used for this manual doesn't have carrier connections switched on, so this page is described from ConsignTrak itself. Carrier connections also haven't yet been used with a live FedEx or UPS account.
Before you start
- Role: Administrator. Nobody else sees Carrier health.
- Settings: carrier connections must be switched on where ConsignTrak runs. If not, the page shows the same error as Carrier credentials.
- You'll need: at least one supply partner with a connected carrier. Without one, every card says Not configured.
Step by step
-
Open your account menu. Choose your initials in the top-right corner, then Carrier health.
-
Read the four cards across the top. They add up every supply partner and carrier. A red card (Signature Rejections or Poll Errors) or an amber one (Reconciliation Flags) means something needs looking at. These cards refresh themselves every 30 seconds.
-
Check the amber banner, if there is one. "N pending events" means messages arrived but haven't been processed yet. ConsignTrak retries them every 5 minutes. One or two that clear on their own are normal. A number that keeps growing is not.
-
Find the problem card under By carrier. Every supply partner has one card for FedEx and one for UPS. The pill in the corner tells you its state:
Pill What it means What to do Healthy Connected, a message arrived in the last 24 hours, and nothing failed in the last hour. Nothing. Stale Connected, but nothing has arrived for 24 hours, or ever. If that supply partner shipped by this carrier today, see the problems below. A partner that didn't ship today is normally Stale. Failing At least one signature rejection (FedEx) or poll error (UPS) in the last hour. This outranks Stale. Usually wrong or out-of-date credentials. Rotate them. Paused Reserved for switching a connection off without deleting it. Nothing sets it today. — Not configured No credentials saved for this carrier. Configure it if the supply partner ships by this carrier. -
Look at Recent events to see what happened. It lists the last 20 messages and checks across every supply partner, newest first. The Outcome says what ConsignTrak did with each one (see the table below). This list doesn't refresh on its own. Reload the page to update it.
-
Work through Reconciliation discrepancies. Each row is a shipment the carrier knows about that ConsignTrak never heard of, found by the nightly check in the last 7 days. Choose Review → to open Pending tracking, where the office attaches it to the right order.
-
Go to Configure credentials (top right) to fix a connection.
Every field and option
Top of the page
| Field or control | What it means | Required | Default | What changes when you set it |
|---|---|---|---|---|
| Configure credentials | Opens Carrier credentials. | — | — | — |
| Events Last Hour | Carrier messages received in the last hour, all supply partners together. | — | 0 | Read-only. Refreshes every 30 seconds. |
| Signature Rejections | FedEx messages refused in the last hour because their signature didn't match the saved secret. Red when above 0. | — | 0 | Read-only. |
| Poll Errors | Times in the last hour that ConsignTrak couldn't log in to UPS or get an answer. Red when above 0. | — | 0 | Read-only. |
| Reconciliation Flags | Shipments the nightly check found missing, last 7 days. Amber when above 0. | — | 0 | Choosing the card opens Pending tracking. |
| N pending events banner | Messages received but not yet processed. Retried every 5 minutes. Shown only when above 0. | — | Hidden | Read-only. |
By carrier (one card per supply partner and carrier)
| Field or control | What it means | Required | Default | What changes when you set it |
|---|---|---|---|---|
| Supply partner name, manufacturer code, FEDEX / UPS | Which connection the card describes. | — | — | Read-only. |
| Status pill | Healthy, Stale, Failing, Paused or Not configured (table above). | — | Not configured | Read-only. |
| Last event | When the last message for this connection arrived. "—" if never. | — | — | Read-only. |
| Events · last hour | Messages received in the last hour. | — | 0 | Read-only. |
| Sig rejections · 1h (FedEx cards) | FedEx messages refused in the last hour. Red when above 0. | — | 0 | Read-only. |
| Poll errors · 1h (UPS cards) | Failed checks with UPS in the last hour. Red when above 0. | — | 0 | Read-only. |
| Reconcile · 7d | Missing shipments the nightly check found for this connection in the last 7 days. | — | 0 | Read-only. |
| Pending events | Messages waiting to be processed. Shown only when above 0. | — | Hidden | Read-only. |
When no supply partner exists yet, the section says No supply partners configured with a Configure credentials button.
Recent events
| Field or control | What it means | Required | Default | What changes when you set it |
|---|---|---|---|---|
| Time | When it happened. | — | — | Read-only. |
| Carrier | FEDEX or UPS. | — | — | Read-only. |
| Source | event: a tracking message being matched to an order. webhook: FedEx calling in. poll: ConsignTrak asking UPS. | — | — | Read-only. |
| Outcome | What happened (next table). | — | — | Read-only. |
| Supply Partner | Whose account it was. "—" when it couldn't be told. | — | — | Read-only. |
| Detail | The technical reason, when there is one. Quote it when asking for help. | — | — | Read-only. |
| Outcome | Plain meaning |
|---|---|
| APPLIED | The box was added to its order. |
| NO_CHANGE | ConsignTrak already had this tracking number. |
| OVERWRITE_BLOCKED | The order already had a different tracking number. Carriers never overwrite one a person entered. Check the order. |
| UNMATCHED | No order matched the label's reference. Usually the order number was missing or mistyped on the label. The office can attach it from Pending tracking or Import tracking. |
| OUT_OF_SCOPE | The reference matched an order belonging to a different supply partner than the account. Check which account printed the label. |
| PENDING | Received, waiting to be processed. |
| REPLAYED | Was stuck, and the 5-minute retry processed it. |
| ERROR | Processing failed. Retried automatically; if it keeps happening, report the Detail. |
| SUCCESS | FedEx's message was accepted, or UPS answered. |
| SIGNATURE_REJECTED | A FedEx message didn't match the saved secret. Rotate the FedEx credentials. |
| OAUTH_FAILED | UPS refused the client ID or secret. Rotate the UPS credentials. |
| FETCH_FAILED | UPS couldn't be reached or gave an error. Usually temporary. |
| DECRYPT_FAILED | ConsignTrak couldn't read its own saved credentials. Enter them again with Rotate. |
| PARTIAL_FAILURE | A message arrived but only part of it could be processed. |
When nothing has happened yet, the list says No carrier events yet.
Reconciliation discrepancies
| Field or control | What it means | Required | Default | What changes when you set it |
|---|---|---|---|---|
| Found at | When the nightly check found it. | — | — | Read-only. |
| Supply Partner | Whose shipment it is. | — | — | Read-only. |
| Filename | The name of the check's record in the tracking import history. | — | — | Read-only. |
| Action → Review → | Opens Pending tracking. | — | — | — |
When there's nothing to review, it says No reconciliation discrepancies.
What happens next
Nothing on this page changes anything. It only reports. Fixes happen elsewhere:
- Credentials are fixed on Carrier credentials. After a rotate, the card should go from Failing back to Healthy within the hour, once a message succeeds and the hour's failures age out.
- Missed shipments are attached to orders in Pending tracking.
- Every message, matched or not, also shows in the tracking import history. See Automatic carrier updates.
Common problems
A card is Failing with signature rejections (FedEx) — The secret in ConsignTrak doesn't match FedEx's, or FedEx is calling an old webhook address after a rotate. Rotate with the secret from the FedEx subscription, then paste the new Webhook URL into FedEx.
A card is Failing with poll errors (UPS) — Look at Recent events. OAUTH_FAILED means the client ID or secret is wrong or was reset at UPS: rotate with fresh values. FETCH_FAILED now and then is UPS being busy and clears on its own.
A card has been Stale all day but the supply partner shipped — Messages aren't arriving. For FedEx, check the webhook address in the FedEx subscription. For UPS, check the shipper number. For both, check that labels carry the order number in the reference field. If everything is right, ask whoever hosts ConsignTrak whether automatic carrier updates are switched on.
Lots of UNMATCHED outcomes — Labels are being printed without the ConsignTrak order number in the reference field. Remind whoever prints labels, and have the office attach the boxes from Pending tracking.
The pending events banner keeps growing — Something fails every time a message is processed. Note the Detail on the newest rows in Recent events and send it to whoever supports your ConsignTrak.