The Transfers Console

Updated Jul 27, 2026

Hosted File Gateway

The Transfers Console

The Transfers tab of Connectors > File Exchange is the record of every file that actually moved — in either direction, and by either mechanism. Files a partner uploaded into the hosted gateway and files a connector collected or delivered are listed together, so "did that file move?" is one question rather than two.

EndpointsTransfersActivityPartnersRoutesSecurity

Reading needs Builder or Viewer; replay needs DataMagik - Builder.

The columns

Column	Shows
When	When the transfer happened.
Direction	An arrow: down for a file that came in, up for one that went out.
Endpoint	Which endpoint carried it — the gateway principal, or the connector we dialled.
File	The path the partner used, not the key we filed it under.
Size	Bytes transferred.
Handler	What claimed the file — edi, script, ocr, app_load, store. Blank for outbound and for anything dedup stopped before routing.
Status	See below. A failure or duplicate shows its reason underneath.
Expires	When the stored object may be removed. `kept` means retention is off for it, a date means it is due then, and `deleted 17 Mar` means the bytes are already gone and only the receipt remains.
From	The address the transfer came from.

Filters

Four controls narrow the list, and they combine:

Direction — both, received, or sent.
Status — any one of the statuses below.
Handler — EDI, Script, OCR, Lookup load, or Store.
Filename or path — a free-text search across both.

"Show me failed OCR from today" is two dropdowns.

The status worth putting on a dashboard is refused. It is the only one where a partner's delivery did not land at all, so it is the one that turns into a phone call.

Statuses

Status	Means	Do
received	Stored and recorded, but nothing was queued — normally because no processing queue is available.	Investigate; replay once it is back.
queued	Matched a route and is waiting for a worker.	Nothing. Refresh.
processed	The handler ran and reported success.	Nothing.
duplicate	These exact bytes were already delivered by this principal. Not reprocessed. The note names the original.	Usually nothing — a partner re-sent.
unrouted	Stored safely, but no route claimed the path.	Add a route, then replay.
failed	The handler ran and failed — or a script rejected the document.	Read the reason in the detail panel.
refused	The endpoint would not accept the upload at all — today, storage quota. The only status where a partner's file was turned away rather than stored.	See Limits.
staged	Placed in `/outbound` for a partner to collect.	Nothing until they collect.
sent / collected	Pushed to a partner's server, or taken by a partner from ours.	Nothing.

A duplicate row shows no handler, because dedup happens before routing — DataMagik never decided what to do with it, on purpose.

The outcome panel

Click any row. The header carries status, handler, size, protocol, the virtual path the partner used, the storage key, the SHA-256, the time, the endpoint and the source address. Below it, Artifacts shows what the handler produced:

EDI — the transaction sets and their actions, linked to the EDI console.
Script — the run status, how long it took, anything it returned, and its console output.
OCR — the extracted fields, kept on the transfer itself.
Lookup load — how many rows were imported and which were skipped, with reasons.
Store — that the bytes were stored.

This panel exists because processed only ever meant the gateway did its part. A script that threw, or an extraction that failed outright, still left a green transfer — the evidence sat in another table. The panel resolves it, so "it says processed, but did it work?" has an answer on the screen.

The stored object is the source of truth, and the receipt outlives it. Once the retention window passes, the file is deleted but the row stays — so "what became of the file that partner sent last quarter?" is answered with "deleted on schedule on the 17th" rather than with silence.

Replay

Replay through the pipeline re-queues the stored file. It re-resolves the route rather than trusting the original decision, so a rule you fixed afterwards actually takes effect. The stored object is untouched.

Use it after: adding a route for an unrouted file, fixing a script that failed, correcting an extraction profile, or registering the trading partner an EDI file needed.

Replay refuses if still nothing matches the path, naming the path so you can see what to write a rule for. The button appears only where replaying means something — an inbound file that arrived at our hosted gateway. There is nothing to route in a staged outbound document, or in a delivery we pushed to somebody else's server, so on those rows it is hidden.

Outbound transfers

Files you have staged for a partner to collect appear with direction out. Staging and collection are recorded separately, and a "Collected" line appears once the partner actually downloads it — which is the question an operator chasing "did they get it?" is really asking.

Deliveries a connector pushed to a partner's own server appear here too. Before the two halves shared a console these were recorded nowhere, and the only answer to "did the partner get the purchase order?" was to read the worker's logs.