Skip to content

DELETE /tms/transloads/break-queue/(?P\d+)

TMS > tms.transload

What it does

#^/tms/transloads/break-queue/(?P<id>\d+)$# accepts DELETE and is declared in app/systems/TMS/transload/api_routes.php:525 as a regex pattern.

The route handler delegates to tmsTransloadApiBreakQueueCancel(). That function is the owner of this behaviour; the route entry is only dispatch.

Call chain:

  1. → tmsTransloadApiBreakQueueCancel() — app/systems/TMS/transload/work_queue_api_helper.php:428
  2. ↳ tmsTransloadApiBreakQueueAssertCanManage() — app/systems/TMS/transload/work_queue_api_helper.php:89
  3. ↳ 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
ID

Success is { "data": …, "requestId": "…" }. Failure is { "error": { "code", "message" }, "requestId": "…" }.

SQL executed

UPDATE T_LOADING_PLANNER

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

  • Break queue id is required.
  • 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.