MLService Prediction Call Failed

News Knowledge Base
1

Points to validate to resolve : "message": "Error while parsing authorization header", while using ML Skill from Studio .

Issue Description: When running the ML Skill from UiPath Studio, it results in the following error

MLService prediction call Failed

{

"code": "Forbidden",

"message": "Error while parsing authorization header",

"stacktrace": null,

"trace_id": null

}

Points / Steps to validate and perform:

  1. Verify if the Robot is connected to Orchestrator
  2. Also, ensure that the robot is created and connected for the same tenant for which AI-Fabric is enabled Most of the time this resolves the issue. (Note: This step is not applicable for hybrid deployments (Orchestrator On-Prem but AI-Center is on UiPath Cloud or vice versa)
  3. Make sure all the required permissions are provided to the role under which the robot is executing the process ( Robot Role)
  4. Go to AI Center Project -> ML Skills and check if the ML skill is present and available or not. If the skill has been stopped, try restarting the skill
  5. Try disconnecting the robot/studio from Orchestrator and reconnecting again and then test the scenario
  6. If you have AI Fabric deployed on Prem and Air-Gapped, ensure Document Understanding pages/AI Units are allocated to the specific tenant under the host license. Again this has been at times the cause of the error. If you using AI Center via UiPath Cloud, ensure that you have Document Understanding pages (legacy license model) or AI Units (new license model) available. You can check this by navigating to your cloud instance -> Admin -> License -> Robots & Services. On this page you should see either Document Understanding pages or AI Units available.

If the issue still persists after performing the troubleshooting steps above, share the following information with UiPath Product Support:

  • After causing the error to occur, run the UiPath Diagnostic Tool on the machine where the issue is occurring and share the report. Read more on the Diagnostic Tool .