The Files section of a file datasource's Source step lists every file the datasource holds. Use it to check what a load reads, fetch new files from a server or bucket, download or delete stored copies, and reload the days whose files changed.
To reach it, open a saved datasource: double-click it in the Lake tree, or right-click it and choose Edit (see The Lake tree), then open the Source step. For where the files come from, see Load files.
For an upload source, the drop area sits at the top of the section, so you can add more files to a saved datasource. Added files are stored right away and loaded by the next run of each table. Days that fall outside a table's sync window appear below for a reload.
The list has six columns:
| Column | What it shows |
|---|---|
| File | The file's name. Point at it for the full stored path and extra lines such as New version of {path}, Stored as {path}, Remote {path} or Source encoding {enc}. |
| Size | The stored size, in units from B to TB; - when it is not known yet. |
| Status | Where the file is in processing; see the badges below. |
| Date | The date found in the file's name or path when a table group extracts one; otherwise -. A ready file whose group expects a date but has none shows no date. |
| Groups | The table groups that match the file, by label. An Excel workbook shows Workbook instead, because its sheets are the tables listed below it. A ready file that no group matches shows No group. |
| Rows | Rows loaded from the latest load; Not loaded until a run reads the file. Point at the figure for the per-table breakdown. |
The Status badges, in one line each:
| Badge | Meaning |
|---|---|
| Uploading | The upload has not finished yet. |
| Processing | Converting to UTF-8 and checking the content. The file is loaded once it is ready. |
| Ready | The file is stored and checked; loads and downloads can use it. |
| Failed | Processing failed. Open the message under the file name for the error. |
| Replacing… | A new version of this file is on its way. Loads keep using the current file until the new one is ready. |
| Replace failed | The new version could not be prepared. The current file is still loaded. |
| Duplicate | Loaded, but the content is identical to {dup}. Both files are read - delete one to avoid double rows. |
Two more states to know:
What the description covers:
Deleting a stored copy never changes loaded data by itself. A day is replaced only when a run reloads it.
For SFTP, FTP and S3 sources, the section opens with a sync card.
| The card says | What it means |
|---|---|
| Fetching files from the server | A fetch is running. New and changed files are copied in the background, and the list refreshes as they arrive. |
| Last sync succeeded | The last fetch finished. Scheduled runs fetch new files before loading; Fetch now copies them right away. |
| Last sync failed | The fetch failed. Fix the cause and fetch again; files fetched before the failure stay available. |
| Last sync finished with warnings | The fetch finished, but some files or post-processing steps reported problems. |
| No sync status yet | Nothing has been fetched yet. Fetch now copies new and changed files from the server. |
| Sync status not refreshed | The sync ran longer than the status check. Click Refresh to see where it stands. |
When stored files changed days that fall outside a table's load window, a banner appears above the list.
For the messages you may see in this section, read Lake troubleshooting.
The file is being prepared: Converting to UTF-8 and checking the content. The file is loaded once it is ready. Wait a moment; the list refreshes on its own, and the file loads only after it turns Ready.
Two stored files hold identical content, so both are read and their rows appear twice. Delete one of the two copies. The badge's tooltip names the file this one matches.
A file that is still being prepared cannot be deleted: its delete icon is disabled with Wait until processing finishes. Wait for the row to settle, then delete it.
No. Rows already loaded stay in the Lake until a run reloads their days. If the deleted files covered days outside a table's sync window, reload them from the banner so the table matches the files.
Because the stored files add up to more than 256 MB, so the zip downloads through the browser in a new tab instead of through the page. A single file above 256 MB downloads in a new tab too.
One reload covers up to 366 days per table, so the button is disabled and the banner asks for a full reload instead; see Run, stop and troubleshoot loads.
A table group extracts a date from each of its files and found none in this file's name or path. Date-incremental loads skip this file, so its rows do not load. Give the file a name that matches the group's date format, or turn the extraction off if the group does not need it.
Fix the cause and fetch again; files fetched before the failure stay available. Click the message line under the card to open Last sync messages for the detail, then click Fetch now.
A fetch is already running or starting, so there is nothing to trigger. Wait for it to finish; the list refreshes as files arrive.
Rows counts the rows loaded from the file in the latest load, with a per-table breakdown in the tooltip; Not loaded means no run has read the file yet. Groups lists the table groups that match the file, by label. Workbook marks a workbook whose sheets are the tables below it, and No group means no table loads this file.