How to request load reactivation, cancellation, or deletion
When a load is cancelled, removed, or accidentally generated on a container, you can request the support team to reactivate or delete it. These operations are not yet available in the UI for customer users.
When to request a reactivation
Reactivate a load when:
- A load was cancelled by mistake.
- A load was archived during a cleanup operation but is still needed.
- The container number is still active and you need to re-link the load.
When to request a deletion
Delete a load when:
- Extra loads were generated automatically and are no longer needed.
- A load was created in error on the wrong container.
- The load has no associated delivery, invoice, or shipment activity.
What to send to support
Send an email to help@julesai.com (or open a chat from the Jules app) with the following:
- Action requested — reactivate, uncancel, or delete.
- List of load numbers — full container codes, one per line, e.g.:
CT2026-05-0014528
CT2026-05-0014529
CT2026-05-0014530
- Parent operation reference (optional but helpful) — e.g.
P2026-05-0-001-401. - Reason (one sentence) — helps support detect side effects.
What happens next
The support team verifies that the loads have no blocking dependencies (active shipments, invoiced quantities, etc.), then performs the change directly in the database. You will receive a confirmation when done. Refresh the order/container page to see the loads reappear or disappear from the list.
Technical context
Load lifecycle (reactivate / cancel / delete) is handled at the operation level in the Jules backend. Cancellations set the load to an inactive state in the loads table without removing it. Deletion permanently removes the row and the linked delivery line. Customer-facing reactivation is on the roadmap but is currently a backend-only operation to prevent inventory and position-report mismatches.
Updated on: 11/05/2026
Thank you!