Tracking the Files Your Launchers Received (Launcher Files)

When a partner says they sent you a file, you need to know what happened to it. Usually you'd look in Flow Execution Search, but a file only shows up there once it starts a flow. If the file didn't match any of your flows, or the launcher failed before it could start one, there's no execution to find. From your side, it looks like the file vanished or never arrived.

The Launcher Files page fills that gap. It lists the files your launchers received in the last 14 days and shows what became of each one: submitted to a flow, filtered out, errored, or still processing. You can confirm a file arrived, see which flows it went to, and find out why it didn't go anywhere, all without opening a support ticket.

Opening Launcher Files

Go to Workspace Settings and click the Launcher Files tile in the Communications section. You need the Owner or Editor role to open the page. Viewers and integration users can't see it.

Which files are recorded

Launcher Files records files received by these launchers. The name in bold is how each one appears in the Launcher column.

• AS2
• CargoWise eAdaptor, which also covers CargoWise eAdaptor Next
• Email
• HTTP
• S3
• Upload Page

Scheduled launchers don't receive a file, so they have nothing to record. SFTP launchers aren't included either, because their files are picked up inside the flow and already appear in that flow's execution logs.

Most launchers record a file even when it doesn't match any of your flows, so you can see it was filtered. A few cases work differently, because we can't always tell which workspace a file was meant for:

• HTTP: a request that doesn't match any flow is rejected right away with a 400 "Invalid Flow" response, so the sender already knows it failed and the file isn't recorded. A request that fails its credential check isn't recorded either.
• Email: an email that doesn't match any flow isn't recorded.
• S3: a file that doesn't match any flow is recorded only when every launcher watching that bucket belongs to your workspace.
• CargoWise eAdaptor Next: acknowledgements aren't recorded, because they report on a file that was already sent rather than delivering a new one.

Searching for a file

Choose a time range, add a file name, identifier, or status if you want to narrow things down, and click Search. You can also press Enter in the search box. Nothing loads until you search.

The quick-range buttons cover the last hour, 24 hours, 7 days, and 14 days, and Last hour is selected by default. For a specific window, set Received after and Received before. Leave Received before empty to search up to now. Records are kept for 14 days, so a range that starts earlier than that only goes back 14 days.

The File name or identifier box looks for an exact match on the whole value, ignoring case. Searching for INV-1001.xml finds inv-1001.xml, but searching for INV-1001 won't. One box covers file names and every identifier in the table below, so you can paste in whatever reference your partner gave you.

The Status filter limits results to one status. Leave it on Any status to see everything.

What each status means

A file appears on the page as soon as it finishes, or about a minute after it arrives if it's still running. So a file that landed seconds ago may not show up yet. Give it a minute and search again.

If a file stays in Processing for 15 minutes, it's marked Errored with "No result was recorded for the file within 15 minutes of receiving it."

Errored isn't always final. Launchers retry many failures automatically, and if a later attempt succeeds, the status changes to Submitted or Filtered.

File identifiers

When a file arrives, Chain.io records identifiers from it so you can search by the reference your partner or your own system uses, not just the file name. Here's what's captured and which launchers capture it:

ISA13 and UNB 0020 are read from the first 4 KB of the file, where the EDI envelope sits. XML, JSON, CSV, and other non-EDI files don't have these, so it's normal for them to be missing.

If you control a system that sends files to an HTTP launcher, set an X-Request-ID header to your own reference for each request. You can then search Launcher Files with the same ID your system logged.

Reading the results

Each row shows when the file was received, the launcher type, its status, the flows it was submitted to, its file name, and its size. When a file was submitted to more than one flow, or has more than one name, the row shows the first and a "+N more" count. Flows are shown with their current names, so a renamed flow shows its new name. A flow that has since been deleted, or that you don't have access to, shows as "Unknown flow."

Expand a row with the arrow to see everything recorded for that file: the error message if it errored, the flows it launched, its identifiers, and any other file names. Each flow under Flows launched links to Flow Execution Search, so you can jump straight to the execution the file started and pick up from there.

Results load 200 at a time, newest first. Click More to load the next 200. The total box and status bar next to the results show how many files matched and how they break down by status.

A search returns at most the newest 2,000 files. If your search hits that limit, the total box shows "2000+" and a message tells you older files in the range weren't searched. Narrow the time range, or search for a specific file name or identifier, to see them.

Downloading results

To export files to a spreadsheet, tick the checkbox on each row you want, or use the checkbox in the header to select every loaded row, then click Download. The CSV includes only the rows you selected, so click More first if you need files beyond the first 200. The file has these columns:

• Received
• Launcher
• Status
• Error
• Flows launched
• File name
• Other file names
• Size (bytes)
• Identifiers

When a cell holds more than one value, such as several flows or identifiers, the values are separated by semicolons.

Error messages

When a file errors, expand its row to see one of these messages:

When you contact support, the quickest way to share a file's details is to select its row and attach the downloaded CSV.

Troubleshooting tips

I can't find a file my partner says they sent

Switch to Last 14 days and search for the most specific reference you have, such as a CargoWise Tracking ID, an AS2 message ID, an ISA13, or the exact file name. If the file arrived in the last minute, wait a moment and search again. Check whether it's one of the unmatched files that aren't recorded, described in Which files are recorded above. For example, an HTTP sender whose request didn't match a flow got a 400 "Invalid Flow" response, so ask them what response they received. Files older than 14 days are no longer kept.

The file was filtered, but I expected it to go to a flow

Filtered means none of your flows accepted the file. Check that a flow is set up and enabled for that launcher, and that the flow's source file filters match the file. See Filters For Source Files In Flow Configurations and Enabling & Disabling Flows.

The file was submitted, but I can't see what happened next

Once a file is submitted, its flow takes over. Expand the row and click the flow under Flows launched to open its execution in Flow Execution Search. For more on what you'll see there, read Finding Flow Executions and Flow Execution Statuses.