Split
This chapter was written from the product's source code and has not yet been checked by a person on a running Cogneris. If what you see on screen differs, the screen is right — please tell your Cogneris contact so the chapter can be corrected.
Split finds where each document begins and ends inside a file that holds several of them — for example one scanned PDF with an identity card, a proof of address and a payslip. The Cogneris Vision service returns the segments it found for each file.
| Palette | Not offered any more: Split keeps the original files instead of separating them, so a new version cannot be published with it. Versions already published keep running it. |
| Outputs | One output. |
| Content status | From source; not observed (workflow-fe f88c5c1, workflow-be 6703373, 2026-10-22) |
A draft that still has a Split node shows Split does not separate documents yet on the node and cannot be published: the service answers The 'split' phase does not separate documents yet: its output keeps the original files. Remove the node and publish again. Remove the node — the phases that follow receive the same files without it. Processes on versions already published keep running Split as described below.
When to use it
When the people who send you documents scan several of them into one file, and a person should see and confirm how that file divides.
Split does not turn the file into separate documents for the rest of the workflow. The phases after it still receive the original files; the segments are kept as the result of the split, for review.
What happens in a run
The phase reads the documents from the output of the phase that leads into it, and handles them one at a time:
- A document that already failed in an earlier phase is not processed again; it is carried forward as skipped.
- The file is sent to the Vision service, which returns its segments.
- The segments are recorded on the document of the run.
The output is one row per document (document, split, and skipped or error when they apply) plus the list of documents — the same files that came in.
The split is kept for human review. In a Manual Review, the reviewer sees it as SPLIT review, with … segment(s). That view only handles PDFs: for any other file it shows SPLIT currently supports only PDFs.
When documents fail
A failure on one document marks only that document failed; the others carry on, and later phases skip it.
- A temporary failure of the Vision service (server error, timeout, connection error, too many requests) is retried up to 3 times for that document. When the service asks to wait at most 10 seconds, the phase waits that long.
- If no document succeeded:
- and a Manual Review is still ahead in the process, the phase completes anyway and the review receives the failed documents for a person to decide;
- otherwise, if every failure was temporary, the whole phase runs again, up to 3 more times;
- otherwise the documents are marked failed and the process fails. If exactly one Send is still ahead, it runs first to deliver the failure, every other pending phase is skipped, and the process then ends as failed.
- If at least one document succeeded, a document whose temporary failure outlasted its retries is marked failed; the phase is not run again for it.
Configuration
Select the node to open Phase Configuration. Its header shows the phase name, Split, and the panel says This phase has nothing to configure.
| Field | What it does | Required | Format / values | Default | Validation messages |
|---|---|---|---|---|---|
| Description | The name shown on the node. | No | Free text. Left empty, the node keeps its previous name. | Split | — |
Common problems
| Message | Cause | What to do |
|---|---|---|
| Auth token missing for run; cannot call the document service. (service text, run error) | The process carries no credential for the Vision service. | Start the process again. If it persists, contact Cogneris support. |
| No documents found for split. (service text, run error) | The phase received no documents. | Check that the phase leading into Split passes documents on. |
| split: no document succeeded — … (service text, run error) | Every document failed. The text lists the error of each one. | Read each document's error, check the files, then start the process again. |
| split: no document succeeded because all failures were transient — … (service text) | Every document hit a temporary failure. The phase is run again automatically. | Wait. If the process then fails, start it again later. |
| SPLIT currently supports only PDFs. | In the review, the document is not a PDF. | Ask for the documents as PDF. |
| Later phases still process the whole file | Split does not create separate documents for the next phases. | Ask senders to upload one document per file when later phases must treat them separately. |
Related
Last reviewed 2026-10-22 · Version 1.0.0 · Owner: product-documentation