Skip to main content

​
Why isn’t my File from Email data source picking up new files?

Each refresh scans the dedicated mailbox for emails that match the configured selectors, so a file only imports when its email clears every filter. The most common reasons a new file is skipped:
  • The sender isn’t on the allow-list. Only messages from a configured sender address are considered. If the file was forwarded or sent from a different address, it won’t match.
  • The subject doesn’t contain the configured substring. The subject filter is a substring match, so a changed subject line can exclude an otherwise-valid email.
  • The file name doesn’t match the filter (attachment mode). When a file-name filter is set, only attachments whose names contain one of the configured fragments are ingested. An empty filter accepts all matching attachments.
  • The email is outside the scan window. Each run only looks back a limited period — one month for attachment mode, three days for download-link mode. An email older than that window on the day it would first be seen is not picked up.
  • The email was already imported. Deduplication prevents the same email from being processed twice, so re-sending an identical file does not create new rows.
Newly-arrived files are not imported instantly; they appear after the next scheduled refresh. For the refresh schedule, see the File from Email data reference. If a configured sender has not sent any matching email within the scan window, the data source reports NO_EMAIL_SENT for that sender.

​
Why did creating my attachment-mode data source fail with NO_FILE_MATCHING_SETTING?

Attachment mode validates at creation that at least one email already matching the configured sender, subject, and file-name filters exists in the mailbox. When no such email is found, setup stops with NO_FILE_MATCHING_SETTING. To resolve it, confirm a qualifying email — correct sender, subject substring, and attachment name — has already been delivered to the mailbox, then create the data source again. Download-link mode skips this setup check, so it can be created before any matching email arrives.

​
Why did my File from Email data source disconnect after a new file arrived?

The connector expects each incoming file to keep the same shape as the columns discovered on the first successful import. A structural change disconnects the data source:
  • INVALID_CSV_MISMATCHED_COLUMN_COUNT — the file’s column count no longer matches the established schema (a column was added or removed).
  • CSV_COLUMN_TYPE_MISMATCHED — a value in a column no longer matches the type inferred for that column (for example, text landing in a column previously read as numeric).
To recover, correct the source file so its columns and value types line up with the original layout, then reconnect the data source. When the upstream schema genuinely needs to change, create a new data source against the new layout rather than sending the changed file to the existing one. No. The delivery mode is chosen when the data source is created and is locked afterward. To move a feed from email attachments to download links (or the reverse), create a new File from Email data source in the other mode and point widgets at it. In download-link mode, the connector extracts a download URL from the email body and fetches the file over HTTPS. Two failures are common:
  • NEED_WHITELIST_IP_FOR_DOWNLOAD_LINK — the link host returned a 403 because it restricts access by IP. The Adriel platform IP address must be added to the host’s allow-list before the file can be downloaded.
  • NO_DOWNLOADABLE_LINK_IN_GIVEN_EMAIL — no qualifying download link was found in the email body. Qualifying links point to csv, tsv, xls, xlsx, zip, gz, or jsonl files, so an email that only links to a landing page or dashboard has nothing to fetch.

​
Why is only part of my XLSX workbook showing up?

For XLSX files, only the first non-empty sheet is parsed; any additional sheets are ignored. When several sheets are relevant, pre-consolidate them into one sheet or split them into separate files, each delivered to its own data source. CSV files carry a single table and are not affected. If a file matches every setting and still fails to import for reasons none of the above explain, email support@adriel.com with the sender address, subject line, file name, and the affected dashboard URL.

​
Common issues

The fileNameToFilter setting on a File from Email data source filters which attachments get cached. If the filter is set too narrowly — for example, to a specific dated filename — newer attachments with different names are ignored.Broaden the filename filter to match every expected file.
For File from Email data sources using APPEND or UPSERT update modes, column names and the overall schema must remain identical across every file. Adding a new header column, renaming a column between deliveries (for example, flipping between channel and Media type), or introducing a column midstream causes every subsequent sync to fail.Fixes:
  • Have the vendor keep the schema consistent across deliveries.
  • Switch to a REPLACE update mode where every file overwrites the last.

File from Email data reference

Import model, field type mapping, refresh cadence, and limits.

Connect File from Email

Set up the mailbox, delivery mode, and matching filters.

File from SFTP data reference

Alternative file feed delivered over SFTP.

File from OneDrive data reference

Alternative file source from cloud storage.