ML Extractor Throws Failed To Consume License Error

How to resolve when the ML Extractor throws error " DocumentUnderstanding server returned 409 (Conflict). Additional details: {"info":"Prediction Failed","reason":"{\"message\": \"Failed to consume license\"}"} " ?

This error occurs if Studio or Robot is not able to consume Document Understanding Units for processing the files.

It can happen because of following reasons

  1. DU units are not available for consumption

If the DU units are not available for consumption, then the ML extractor would throw the error. For cloud AIC/on-prem non-airgapped AIC, licensing happens in cloud account and for airgapped AIC, licensing happens at on-prem Orchestrator (Refer Document Understanding Docs - AI Center Relation To DU ). The DU license can be checked for different deployments as below

  1. Automation Cloud / On-prem non-airgapped AIC

Login to automation Cloud account and navigate to Automation Cloud Home -> Admin -> Licenses -> Robots & Services and check if DU units are available under Document Understanding section or not

  1. On - Prem airgapped AIC

In the On-prem Orchestrator, login to host tenant if licensing is being done at host level and to the tenant to which the studio is being connected to if licensing is being done at tenant level. Navigate to licenses section (Refer to this link - https://docs.uipath.com/orchestrator/docs/managing-your-licenses on how to navigate to licenses section in both cases) and check if DU units are available under Document Understanding section.

Fig: DU units in Orchestrator licensed at host level

Fig: DU units in Orchestrator licensed at tenant level

  1. DU units are available at host level but not allocated to the required tenant

In automation cloud, the DU consumption is only possible at account level. Hence, this should not be an issue in cloud scenario.

However, if DU units are available at host level in On-prem Orchestrator, the DU units need to be allocated to the specific tenant to which the Studio is connected to. Kindly refer to link below on allocating licenses to tenant at host level.

Read more on Managing Your License Allocating Licenses .