Quick answer
ABBYY Vantage transactions get stuck or fail for one of five reasons: the platform is saturated and queuing work while it scales, a skill counter in your subscription has reached its limit, a job-execution error from a network timeout or third-party API call, documents parked at the Manual Review stage, or a failed input or export connection on either end of the skill. Start in Skill Monitor — filter by Status, then by Stage — and read the transaction’s event log before restarting anything.
01 — What You’re Seeing
The documents went in. The results never came back.
Confirm you’re on the right page before you touch anything.
One or more of these signatures, on a Vantage tenant that normally hums:
- Transactions sit in Processing far longer than the skill usually takes — throughput has collapsed, but nothing reads as an error.
- Transactions flip to Failed with job-execution errors — ABBYY’s documentation names network timeouts, third-party API call failures, and Vantage platform issues as the class.
- Uploads are rejected with
Failed to process document. Skill counter has reached the limit— and per ABBYY, the same error can fire invisibly in the background of a document flow. - A held transaction’s event log shows “Reprocessing started” — ABBYY’s event for processing restarted because it was not completed within the allotted time.
- Files land in the SFTP or mail input folder and no transaction is ever created (“Create Transaction Failed” — community-reported, with no published answer) — or work completes and never reaches the export target.
The hard part is that Vantage is ABBYY’s cloud. There is no service to restart, no queue database to query — the platform dashboard belongs to the vendor, and your side of the evidence is Skill Monitor, the subscription counters, and the connections at each end. That turns out to be enough. (The full set of what can be watched from outside the tenant is in the Reveille for ABBYY technical overview, ungated.)
02 — Causes, Ranked by Likelihood
Five causes account for nearly every case
Confirm before you fix — each cause has a cheap, specific test.
| # | Cause | How to confirm | Fix, in short |
|---|---|---|---|
| 1 | Platform saturation or scale-up lag — queued, not broken | Skill Monitor shows transactions waiting in Processing with no failures; your input volume just spiked; status.abbyy.com reports degraded processing. | Smooth the input burst and wait out the scale-up — ABBYY scales system-wide in about five minutes. |
| 2 | A skill counter or license ran out — rejected, not queued | The exact error above on upload or in background flows; check the subscription’s counters — most often Core Cognitive Skills — and license expiration. | Ask your ABBYY account manager to extend the exhausted counter. |
| 3 | Job-execution errors — timeouts, third-party APIs, platform issues | Status = Failed; the transaction’s event log (Show Log) names the step that errored or was restarted. | Restart from Skill Monitor — unless the skill was republished since, in which case create a new transaction. |
| 4 | Parked at Manual Review — waiting on people, not compute | The Stage filter shows the backlog under Manual Review rather than Automatic. | Staff the review queue; a reviewer can take over an open task with the other user’s changes saved. |
| 5 | Input or export connection failed — broken at the ends | Files aging in SFTP or mail input folders with no new transactions; completed transactions that never export. | Restore the connection, re-authenticate the API client, confirm the export database or content services target. |
Cause 1 surprises people because nothing is wrong. Per ABBYY’s own guidance on Vantage processing speed, users cannot directly speed up processing: each skill activity runs on its own pool of microservices, scaling is system-wide rather than per tenant, overload scale-up takes roughly five minutes, and processing times can temporarily rise by up to 30 percent. A tenant that persistently overwhelms the system gets capped, with the excess transactions queued for later. The queue is the design.
03 — The Fixes
Work them in repair order
Reading the evidence first beats resubmitting things at random.
1. Read Skill Monitor before touching anything
Filter transactions by Status — New, Processing, Processed, Failed, or Canceled — then by Stage, Manual Review or Automatic. Open Show Log on a held transaction: the event trail (Workflow Created, Job Started, Job Completed) shows exactly which step the workflow is held up at. A log full of “Reprocessing started” events means jobs are timing out and being retried, which points at cause 1 or 3, not at your skill.
2. Separate slow from stuck
Check status.abbyy.com — ABBYY reports platform slowdowns there. If the platform is healthy and your transactions are queued behind a burst you created, the fix is on your side of the boundary: smooth the input. ABBYY is explicit that duplicating a skill or splitting document flows will not inherently boost performance unless the actual bottleneck — SFTP or mail-folder uploads — is addressed first.
3. Check the counters before the workflow
If uploads are rejected with Skill counter has reached the limit, no amount of restarting helps: a counter in your subscription — most commonly Core Cognitive Skills — is exhausted, and per ABBYY’s knowledge base the fix is contractual: your ABBYY account manager extends the limit. Check days to license expiration while you’re there — an expired subscription produces the same silence.
4. Restart failed transactions — the right way
Per ABBYY’s Skill Monitor documentation, transactions with job-execution errors — network timeouts, third-party API call failures, or Vantage platform issues — are eligible for reprocessing. One sharp edge: if you republished the skill after the failure, a restart runs the old skill version and will likely fail again — create a new transaction instead. And if your transactions have been failing intermittently with internal errors under sustained load, ABBYY fixed exactly that in the Vantage 3.4.1 release — worth confirming your tenant is past it.
5. Walk both ends, then preserve the evidence
Confirm the SFTP and mail input folders are being consumed — files aging there mean transactions were never created, the failure mode community threads report as “Create Transaction Failed,” with no published vendor answer beyond opening a support request. Then confirm the export side: the database connection, the target content services connection, the SFTP output folder. Finally, pull the event logs for anything you intend to investigate: transactions are deleted after the retention period — two weeks by default, regardless of status — and a purged transaction is an incident with no evidence.
04 — How to Stop It Recurring
The platform is ABBYY’s. The deadline is yours.
Every cause above is visible from outside the tenant — if something is looking.
Nobody outside ABBYY can see inside the Vantage microservice pools, and nobody needs to. Every failure mode on this page announces itself at the boundary: queues deepening, counters running down, Failed counts climbing, manual-review backlogs aging, input folders not draining. Platform SLA is not workflow SLA — ABBYY’s status page can be green while your invoices age past their service level — and the boundary signals have to be watched continuously, because no one opens Skill Monitor on a day nothing seems wrong.
That is what Reveille watches, out of the box, through the same APIs you’d check by hand: Check ABBYY Vantage Skills Monitor — Processing, Extraction, Classification, Assembling, and OCR for the queues; Check ABBYY Vantage Active Transactions, Transaction Steps, and Check ABBYY Vantage Transactions Error Log for causes 1 and 3; Check ABBYY License Page Count/Utilization and Days to License Expiration for cause 2; Check ABBYY Vantage Cloud Manual Review Login for cause 4; and Check SFTP input folder, SFTP input exception folder, export database connection, and target content services connection for cause 5. A four-test synthetic path — Create Empty Transaction, Upload File, Start Transaction, Transaction Completion — proves the pipeline end to end on a schedule, so “Vantage stopped taking work” is an alert, not a Tuesday-morning discovery.
Reveille for ABBYY
Reveille for ABBYY provides over 170 ‘out-of-the-box’ ABBYY-specific tests and over 280 ABBYY dashboard metrics across FlexiCapture, FlexiCapture Cloud, Timeline, and Vantage — including every transaction, counter, and connection check above. See Reveille for ABBYY →
Supporting client estates as an MSP, SI, or ISV? That’s what Reveille SENTRY is built for — multi-tenant observability for the estates you manage.
Before the queue ages past its service level
See the Vantage transaction checks run against a live environment.
Enter a business email and the platform you run. The demo environment opens with the Skills Monitor, Active Transactions, and license checks already configured.
No credit card · Nothing to install · Runs on Reveille’s sample estate. Want the list first? Read the ABBYY technical overview.
Quick answers
