Skip to main content

As of late last week 5/30, I’ve noticed the Document Extraction action for Extract Data is failing with a status 425 error due to image processing error with my task bots process. I’ve never encountered this error before till recently. No changes have been made to the learning instance, task bot or user roles. Also, this action package has the latest package update 3.36.10.

 

Status Code: 425
Status Message: IMAGE_PROCESSING_ERROR
Status: DW_EXTRACT_FAILURE

The consumed documents are always pdf files that meets specs per Automation Anywhere criteria. Prior to this, that extraction always provided a status 200 with the extract outputs. Now they are mostly 425 status error although few document extractions are 200. 

Is anyone experiencing issues with status 425 error?

Hi ​@aadewale86,

 

  1. Test with Different PDFs:

    • Try a few PDFs with different layouts or sources to see if the issue is document-specific.

  2. Roll Back or Re-Test with Older Package:

    • If possible, test with a previous version of the Document Extraction package (e.g., 3.36.9) to isolate if the issue is version-related.

​@Tamil Arasu10 Hello, I’ve tried your recommendations but the problem still persists. 

Hi ​@aadewale1986,

 

When a user uploads a document manually, Windows DLP—likely part of Microsoft Purview or another enterprise-level endpoint protection mechanism—detects it as potentially sensitive content. This triggers a prompt requesting the user to provide a justification before proceeding.

However, when the same file is accessed automatically by BotAgent via the Document Extraction package, it lacks the capability to offer such justification. Consequently, the DLP system quietly blocks access to or processing of the document, leading to a silent failure in the automation workflow. This behavior may explain the 425 status error, commonly associated with "Precondition Failed"—a sign that client-side constraints prevented successful execution of the request.

 

Source: Microsoft
Source: Microsoft

If so, you need to work with your security team to disable the DLP (if possible). Once this is done, the documents will start to process normally.

 
 

​@Padmakumar I have ruled out Windows DLP as the issue. This issue still persist

​@Padmakumar I have ruled out Windows DLP as the issue. This issue still persist

 

I recommend raising a support ticket.

 

Reply


Terms & ConditionsCookie settings