DELETE /tms/transloads/work-assignments/(?P\d+)¶
What it does¶
#^/tms/transloads/work-assignments/(?P<id>\d+)$# accepts DELETE and is declared in app/systems/TMS/transload/api_routes.php:507 as a regex pattern.
The route handler delegates to tmsTransloadApiWorkAssignmentCancel(). That function is the owner of
this behaviour; the route entry is only dispatch.
Call chain:
- →
tmsTransloadApiWorkAssignmentCancel()—app/systems/TMS/transload/work_queue_api_helper.php:359 - ↳
tmsTransloadApiBreakQueueAssertCanManage()—app/systems/TMS/transload/work_queue_api_helper.php:89 - ↳
tmsTransloadApiBreakQueueCanManage()—app/systems/TMS/transload/work_queue_api_helper.php:84
Who calls it¶
No literal caller path was found in frontend/, public/ or new-system/.
The endpoint may be called through a constructed path, a helper wrapper, or only by
an external client. Treat the route table and owner function as the authority.
Input¶
| Where | Key |
|---|---|
path |
id |
Request bodies must not use TYPE, ACTION or USERNAME as contract fields.
Output¶
| Key |
|---|
CANCELLED_AT |
ID |
STATUS |
Success is { "data": …, "requestId": "…" }.
Failure is { "error": { "code", "message" }, "requestId": "…" }.
SQL executed¶
UPDATE T_LOADING_PLANNER SET JOB_STATUS='CANCELLED', JOB_END_TIME=?, FINAL_DRAFT=? WHERE CLIENT_ID=? AND ID=? AND JOB_STATUS='SCHEDULED' AND SPECIAL_INSTRUCTION='QUEUE_WORK_ASSIGNMENT' AND DELETED_AT IS NULL
Data¶
Tables reached from the owner function:
T_LOADING_PLANNER
Access¶
- module-gated on
tms.transload, so tenant module access applies
Validation and failure messages¶
- Only assigned work can be cancelled.
- Assignment changed. Reload and try again.
- Manager permission is required.
These strings come from the owner function and are the messages a client can receive. They are also the cheapest way to tell a rejected request from a broken one.