Quick answer
ABBYY FlexiCapture batches stop processing for one of five reasons: Processing Stations that lost their connection to the Processing Server, a failed or exhausted licensing service, a stalled Processing Server queue, database pressure on the FlexiCapture databases, or failed input and export connections. Start in the Processing Server monitor — station status first, then the license.
Scan operators are scanning. The batches land — and then they sit. Nothing moves to recognition, nothing reaches verification, nothing exports. In an Intelligent Document Processing (IDP) pipeline feeding invoices, claims, or onboarding, a FlexiCapture stall is a production outage that announces itself hours later, downstream, as missing work.
Here are the five causes in order of likelihood and the fix for each — complete, on this page. (The full catalog of ABBYY health checks and tests is published here, also ungated.)
01 — The Causes
Five causes, ranked by likelihood
Match the symptom, then jump to the fix.
| # | Cause | The signature | The fix, in short |
|---|---|---|---|
| 1 | Processing Station lost its server connection | Station … can not be started. Error: There is no connection to station; stations show offline in the Processing Server monitor | Restore the station service, account, or network path |
| 2 | Licensing service down or license exhausted | Errors referencing the ABBYY Product Licensing Service; everything “running,” nothing processing | Restart the licensing service; check page count and expiration |
| 3 | Processing Server queue stalled | Tasks pile up at one stage; batches frozen at scanning or recognition | Requeue stuck tasks; rebalance station capacity |
| 4 | Database pressure | Timeouts, deadlocks, transaction-log growth on the FlexiCapture databases | Fix the database, not the stations |
| 5 | Input or export failure | Hot folders filling with aging files, or batches complete but never export | Restore the share, mailbox, or export connection |
Cause 1 does the most damage per minute. FlexiCapture distributes work across Processing Stations; when one drops its connection — stopped service, rotated service account, a firewall or DNS change — its tasks queue behind whatever stations remain, and throughput degrades before it fails outright. Cause 2 is the quiet one: every processing action checks the License Server, so a dead licensing service — or an exhausted page count — stops the estate cold while every Windows service still shows green. Causes 3 through 5 are covered in ABBYY’s own stage-by-stage notes, one page per symptom — the fix sequence below consolidates them.
02 — The Fix
The repair sequence
In order. Restarting stations before checking the license wastes the hour.
-
Open the Processing Server monitor and read station status
Offline or errored stations point to cause 1. On each, confirm the Processing Station service is running, the service account authenticated (password rotations bite here), and the server is reachable from the station — then reconnect.
-
Verify licensing before anything else “running”
Confirm the License Server service is up and reachable from every processing host, then check remaining page count and expiration. An exhausted license mimics a healthy-but-frozen estate perfectly.
-
Clear the stalled queue
In the Processing Server monitor, find the stage where tasks accumulate. Requeue stuck tasks, and if one heavy project is starving the rest, rebalance which stations serve which stages.
-
Check the Windows Event Log and the databases
Processing Server and Processing Station events name the failing component. If errors are timeouts, look at the FlexiCapture database: size, transaction log, deadlocks. Database pressure surfaces as “random” station failures.
-
Walk the pipeline ends
Confirm hot folders and import mailboxes are being consumed — files aging in an input share mean batches were never created. Then confirm exports are landing; batches that finish but never leave block from the other end.
03 — Prevention
How to stop it from happening again
Every one of the five broadcasts itself before work stops.
Stations drop before queues build. Page counts run down before they run out. Hot folders age before anyone calls. The failure repeats in most FlexiCapture estates because nobody watches those signals between incidents — services “running” is not work moving. Reveille for ABBYY FlexiCapture ships over 170 out-of-the-box ABBYY tests, and the ones for this exact chain are pre-configured: connectivity of the ABBYY Processing Server, Processing Station, License Server, and Application Server; ABBYY License Status; Queued Batches, Aging Batches, and Exception Batches; Hot Folders Currency; and the Windows Event Log checks for Processing Server and Processing Station events. When a threshold trips, Reveille can conditionally trigger self-healing recovery — including PowerShell-based scripts that restart required ABBYY services — so step one of the sequence above runs before the queue notices.
Reveille for ABBYY
Agentless tests for stations, licensing, queues, and hot folders — with over 280 ABBYY dashboard metrics for capture service levels. The full catalog is linked above, ungated.
Live webinar · Sept 23
You deployed FlexiCapture successfully. Now assure it.
Reveille and ABBYY, live: keeping FlexiCapture estates processing — stations, licensing, queues, and the watch that catches all five causes above.
Save a seat — Sept 23Frequently asked questions
