Autopilot For Everyone - Enable index in Context Grounding

[martin.parovski]

I’m trying to use Autopilot for Everyone to read a PDF file that has been uploaded to a Storage Bucket in Orchestrator. I’m already connected to the correct tenant and folder, and Autopilot for Everyone works without any issues initially.

However, once I enable the index in Context Grounding and restart Autopilot, I encounter the following error message:

"Oops! Looks like something went wrong during the ECS Initialization. This was the error received: general_http_error
Support telemetry session ID: E+4cHYIR9IDDOSUP3/UcS/"

If I remove the index from Context Grounding and restart the Autopliot then I can continue using autopilot.

Any idea how this error can be solved?

[bhavesh.choubey]

Check File Format and Encoding

• Ensure the PDF is not scanned (image-based) —Autopilot needs text-based PDFs for proper indexing.
• Try uploading a simple text-only PDF as a test — if it works, the issue may be with the specific PDF you uploaded.

Check File Permissions

• Ensure your storage bucket is
  • In the same folder where Autopilot is being used
  • You have read access to it
• Try downloading the file manually from the bucket to ensure access is working.

Limit File Size

• ECS indexing may fail if the file is too large or has too many pages.
• As a test, upload a small PDF (e.g., 1–2 pages) and add it to Context Grounding. If that works, your original file might be too large or complex.

Avoid Special Characters in File Name

• File names with characters like #, +, %, or spaces can cause issues with URL encoding.
• Rename the file to something simple like invoice.pdf and re-upload.

Clear and Reconfigure Context Grounding

• Remove the current grounding config.
• Restart Autopilot.
• Re-add the index only after verifying the file format and size.

if you find your solution then mark this as SOLUTION

Happy Automation

[martin.parovski]

@bhavesh.choubey

Avoid Special Characters in File Name

Thank you @bhavesh.choubey for your quick response. I followed all of your suggestions carefully. This time, I used a one-page PDF file named testfile.pdf, containing only text. Unfortunately, I’m still encountering the same error.

[bhavesh.choubey]

Try Using a File Uploaded During Grounding Setup

Instead of picking an existing bucket file:

• Go to Context Grounding > Add Indexed File
• Upload the testfile.pdf right there from your machine, instead of choosing from bucket

If this works: ➜ problem is with Storage Bucket access by ECS, not the file or ECS.

Test with a Different Storage Bucket

• Create a new Storage Bucket in the same folder.
• Upload a simple test PDF.
• Reconfigure grounding with that file.

If this works: ➜ your original bucket has a hidden permission or scope problem.

Use the “Upload and Index” Option**

If available, use:

• “Upload and Index” → upload the file from local storage rather than selecting from an existing bucket.

This is known to bypass some of the token-based fetch failures from Storage Bucket access.

Contact UiPath Support with Session ID

If all else fails:

• Provide the telemetry session ID:

E+4cHYIR9IDDOSUP3/UcS/

And explain that it fails only when using indexed files from Storage Buckets.

[martin.parovski]

I’ve resolved the issue. I’m not entirely certain if this was the root cause, but in addition to disabling and re-enabling the index form Gontext Grounding, I also deleted and recreated it, directly in Orcestrator->Indexes"