Skip to content

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

TMS > tms.transload

What it does

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

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

Call chain:

  1. → tmsTransloadApiBreakQueueStart() — app/systems/TMS/transload/work_queue_api_helper.php:531
  2. ↳ tmsTransloadApiBreakQueueRow() — app/systems/TMS/transload/work_queue_api_helper.php:609

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
JOB_START_TIME

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

SQL executed

SELECT ID, LOADER_NAME, COMMODITY_NAME, JOB_STATUS, JOB_START_TIME, LAST_SENT_TIME

Data

No table reference is visible in the owner function body.

Access

  • module-gated on tms.transload, so tenant module access applies

Validation and failure messages

  • Break queue id is required.
  • Break queue row was not found.

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.