Skip to main content
Question

Document Automation Repeatedly Going to Validation with “0 Fields to Validate”

  • Sep 2, 2026 5:43 AM UTC
  • 5 replies
  • 111 views

I am facing an issue with Automation Anywhere Document Automation where a document repeatedly goes back to the Validation stage.

The document is processed and sent for validation, but when I open it in the Validation Station, it shows “0 Fields to Validate.” Even though there are no fields requiring validation, the document keeps returning to the validation queue instead of completing the process.

Current behavior:

  • Document is processed by Document Automation.

  • It is sent to the Validation stage.

  • Validation shows “0 Fields to Validate.”

  • After completing/submitting the validation, the same document again appears for validation.

  • This cycle keeps repeating.

Expected behavior:
If there are 0 fields requiring validation, the document should complete the validation stage and proceed to the next stage instead of returning to validation.

Could you please advise what could cause this behavior and how we can prevent the document from repeatedly entering validation?

5 replies

MD 4411
Cadet | Tier 2
Forum|alt.badge.img
  • Cadet | Tier 2
  • Sep 2, 2026 6:53 AM UTC

Try to check if u add any fields as Mandatory , change it to optional


  • Author
  • Cadet | Tier 2
  • Sep 2, 2026 8:29 AM UTC

​@MD 4411 

Thanks for the suggestion. I already checked the field settings, and there are no mandatory fields causing the issue. However, the document still keeps going back to Validation and shows “0 Fields to Validate.”

I currently have Test Mode enabled in Document Automation. Could Test Mode be the reason the document is repeatedly being sent to Validation?
 


Dineshkumar Muthu
Flight Specialist | Tier 4
Forum|alt.badge.img+1

Hi ​@sruthy.v_0 

Based on how Document Automation handles validation, there are two configuration areas that commonly cause this “infinite validation” loop:

  1. Check if Test Mode is enabled for the Learning Instance

In Test Mode, documents are always routed to the validation queue, even if all fields are valid and no errors are shown:

  • “When you process documents in test mode, the documents are moved to the validation queue regardless of whether fields need validation or data extraction was successful…” 
  • “Documents processed in test mode will always be in the validation queue because they are used to compare extraction results.”

If your learning instance is in Test Mode, the behavior you’re seeing (document repeatedly appearing in validation with “0 Fields to Validate”) is expected.

Action:
On the Learning Instances page, verify whether Test Mode is enabled for that learning instance. If you want the usual “process → optionally validate → complete” flow, disable Test Mode and reprocess the document.

 


Dineshkumar Muthu
Flight Specialist | Tier 4
Forum|alt.badge.img+1

​@MD 4411 

Thanks for the suggestion. I already checked the field settings, and there are no mandatory fields causing the issue. However, the document still keeps going back to Validation and shows “0 Fields to Validate.”

I currently have Test Mode enabled in Document Automation. Could Test Mode be the reason the document is repeatedly being sent to Validation?
 

Yes, Test mode will cause this problem. 


KhaledMostafaMe
Most Valuable Pathfinder
Forum|alt.badge.img+2
  • Most Valuable Pathfinder
  • Nov 12, 2026 8:45 PM UTC

@sruthy.v_0  Your "0 Fields to Validate" count is accurate. The document is not stuck on a field. Test mode is sending it back to the queue on purpose.

Test mode is the cause. A learning instance in test mode sends every processed document to the validation queue, even when no field needs validation, so the document will keep coming back until you turn test mode off.

The mechanism is simple. In test mode, Document Automation keeps each document in the queue so developers can compare extraction results across versions. Submitting the validation does not complete the document, because the queue is the designed destination for test-mode runs.

  1. Why it shows "0 Fields to Validate": the validator counts only fields that need correction. Test mode queues the document whether or not any field needs correction, so the count is zero while the document is still in the queue.

  2. Why Submit & Reprocess does not move it on: Submit & Reprocess reruns the document in the same test-mode version, so it lands in the queue again. Fix this by changing the setting, not the document.

  3. What to change: open Document Automation , select your learning instance, and turn off the Test mode toggle on the learning instance page. Then process a new document. The toggle is the only setting that controls this loop.

Test mode is still useful while you tune extraction. Keep it on for experiments and turn it off before you run real volume. The Validate documents in test mode page states the queue behavior directly, and the Enable test mode for learning instances page shows where the toggle lives.