After you implement recognition and validation, you must run the document creation and integrity checking tasks in their own task profile to handle document integrity failures.
In the Document Assembly topics, the TravelDocs application completes recognition and validation before it branches to the FixUp job. This routing was not a problem because you did not implement recognition and validation. Now that recognition and validation are implemented, some pages have Status = 1, which indicates low confidence values or validation errors. The Taskmaster DotScan FixUp task does not finish a job when there are pages with Status = 1.
You must move the document creation task and the integrity checking task out of the Profiler task profile and into their own task profile. Now, you can correct any batch integrity problems before the recognition and validation tasks are run.
