Skip to content
DASH Help Center

Automated ingestion troubleshooting

When automated ingestion misbehaves, the cause is almost always visible on the source channel itself: its last poll status, last error message, and current state. Start there, then work through the common cases below.

A certificate is stuck in “Ingest failed”

Section titled “A certificate is stuck in “Ingest failed””

If a document was found but could not be read or mapped, its certificate lands in Ingest failed instead of Awaiting approval.

  • Check the file type matches the channel. A PDF-mapped channel expects PDFs, and a CSV or Excel channel expects spreadsheets. If the wrong kind of file was pulled in, the ingest is refused. Point the channel at a source that only holds the expected file type.
  • Check the definition map still fits the document. If the document’s layout changed, the map may no longer find the right fields. Run a dry-run to see the mismatch, then update the map.
  • Retry the certificate. A certificate in a failed state can be retried, which resumes processing from the failed step. See Submit & track status.

Duplicate documents

Section titled “Duplicate documents”

DASH de-duplicates automatically — each document is recognised by the source’s own identifier and by a hash of its content, so a renamed or re-uploaded file is skipped rather than ingested twice.

  • If you expected a document to be picked up but it was skipped, DASH has seen identical content before. A genuinely new version must differ in content to be treated as new.
  • If you see two certificates for what looks like the same document, check whether the content actually differs (for example, a corrected value or an added signature) — different content is treated as a new document by design.

Nothing is being ingested

Section titled “Nothing is being ingested”

If new documents are appearing at the source but no certificates show up, check these in order:

  1. Is the channel active? A paused channel does not poll. Resume it — see Configure polling.
  2. Is a poll interval set? An empty interval disables scheduled polling. Set an interval of at least 60 seconds.
  3. Is a definition map pinned? A channel with no map cannot poll. Pin one and run a dry-run to confirm it works.
  4. Was the channel disabled by an error? Repeated authentication failures disable a channel automatically, and a configuration error (such as a missing required field) disables it immediately. Read the last error message, fix the cause, and resume — resuming clears the failure count.
  5. Does the start point exclude the documents? If you chose From today or From a specific date, older documents are intentionally out of range. Review your start point.
  6. Do the documents match the channel’s file filter? A channel restricted to one file type ignores everything else at the source. Confirm the documents are the expected type.

Credential and connection errors

Section titled “Credential and connection errors”

If the channel cannot reach the source at all — a rejected login, an expired token, or an unreachable endpoint — the fix is at the channel connection level.

Section titled “Related”