Skip to main content
Question

Document Automation fails after extraction. 500 unexpected error


Forum|alt.badge.img+6

I’m having issues using document automation recently. It was working fine for weeks, and no changes were made to the process. 

The same process works fine on my local machine.

When we publish this and run it on the botrunner machine, it fails.

 

Looking at the logs, it seems to be related to SSL certificate issues with OpenAI.

DA: Gateway Connection failed! HTTPSConnectionPool(host='MYHOSTNAME.my.automationanywhere.digital', port=443): Max retries exceeded with url: /cognitive/v3/apigee/auth?svc=regional&usecase=openai&basecase=openai (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)')))

What sort of troubleshooting should I be doing for this?

There are many other 500 response codes throughout the botrunner log file, but they all report “unexpected error” with no good information.

lambda$documentMetrics$0(BotInsightMetricsPublisher.java:38) - DocumentMetrics returned with unknown response expected 204 but got 500 and body {"code":"generic.server.exception","details":null,"message":"An unexpected problem occurred"}
2025-Mar-21 Fri 08:32:31.283 INFO  [BotRunner-5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b] - com.automationanywhere.iqbot.infrastructure.restclient.RestClientV2 {CORRELATION_ID=5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b, deploymentId=5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b, traceId=62173acd71134b5b} - doHttpRequest(RestClientV2.java:247) - request url:https://MYHOSTNAME.my.automationanywhere.digital/cognitive/v3/documents/b13e2d47-b5d0-42fb-b6fe-88952af7a312?documentType=INPUT_FILE&actionType=GET response code:500, correlationId: [X-Correlation-Id: 5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b]
2025-Mar-21 Fri 08:32:31.290 ERROR [BotRunner-5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b] - com.automationanywhere.iqbot.infrastructure.restclient.RestClientV2 {CORRELATION_ID=5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b, deploymentId=5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b, traceId=62173acd71134b5b} - isHttpOK(RestClientV2.java:274) - Http response status:500 , headers:[Date: Fri, 21 Mar 2025 12:32:31 GMT, Content-Type: application/json, Transfer-Encoding: chunked, Connection: keep-alive, Cache-Control: no-cache, no-store, max-age=0, must-revalidate, Content-Security-Policy: default-src 'self' https://aai-artifacts.my.automationanywhere.digital/ https://fotts.azureedge.net/ https://static2.sharepointonline.com/ https://res.cdn.office.net/ http://127.0.0.1:22113/ https://cdn.pendo.io/ https://app.pendo.io/ https://data.pendo.io/ https://pendo-static-5673999629942784.storage.googleapis.com/ https://pendo-io-static.storage.googleapis.com/  'unsafe-eval'; img-src 'self' https://aai-artifacts.my.automationanywhere.digital/ https://fotts.azureedge.net/ https://static2.sharepointonline.com/ https://res.cdn.office.net/ https://*.amazonaws.com/ https://*.googleapis.com/ https://cdn.pendo.io/ https://app.pendo.io/ https://data.pendo.io/ https://pendo-static-5673999629942784.storage.googleapis.com/ https://pendo-io-static.storage.googleapis.com/ ; connect-src 'self' https://aai-artifacts.my.automationanywhere.digital/ https://fotts.azureedge.net/ https://static2.sharepointonline.com/ https://res.cdn.office.net/ http://127.0.0.1:22113/ https://cdn.pendo.io/ https://app.pendo.io/ https://data.pendo.io/ https://pendo-static-5673999629942784.storage.googleapis.com/ https://pendo-io-static.storage.googleapis.com/  https://*.amazonaws.com/ https://*.googleapis.com/ https://*.automationanywhere.digital/, Expires: 0, Pragma: no-cache, Referrer-Policy: same-origin, Strict-Transport-Security: max-age=31536000; includeSubDomains; preload, X-Content-Type-Options: nosniff, X-Correlation-Id: 5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b, X-Frame-Options: SAMEORIGIN, X-Xss-Protection: 1; mode=block] , body:{"code":"generic.server.exception","details":null,"message":"An unexpected problem occurred"}
2025-Mar-21 Fri 08:32:31.290 FATAL [BotRunner-5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b] - com.automationanywhere.iqbot.botcommand.commands.download.DownloadCommandCommand {CORRELATION_ID=5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b, deploymentId=5df90524-ad9e-4771-b214-f425cc2c5a55_62173acd71134b5b, traceId=62173acd71134b5b} - execute(DownloadCommandCommand.java:130) - Download Command Failed. Reason: Failed to fetch Document URL java.lang.RuntimeException: Download Command Failed. Reason: Failed to fetch Document URL

 

10 replies

Lu.Hunnicutt
Pathfinder Community Team
Forum|alt.badge.img+11
  • Pathfinder Community Team
  • 66 replies
  • March 21, 2025

Let me tag some folks who may be able to support you with this!

@Aaron.Gleason 

@asif.shaikh 

@Ganesh Bhat 

 


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • 539 replies
  • March 21, 2025

If it is working fine on your local computer but failing with the bot runner, I would contact your IT department to see what could be different. Is there a proxy in place? Can they run Wireshark on the bot runner machine to see what is failing?


Forum|alt.badge.img+6
  • Author
  • Navigator | Tier 3
  • 17 replies
  • March 21, 2025
Aaron.Gleason wrote:

If it is working fine on your local computer but failing with the bot runner, I would contact your IT department to see what could be different. Is there a proxy in place? Can they run Wireshark on the bot runner machine to see what is failing?

We will be trying some of this. I’ve been working with our network admin to see if there is anything he can see.

The VM doesn’t have any sort of proxy and the firewall rules are all pretty much open.

I’ve enabled the deepest level of logging for a run and have been combing through this as well.

No proxy settings get detected after trying multiple locations.

getProxySelector(AAProxySearchStrategy.java:58) - Detecting proxy settings.
readSettings(AAWinProxySettingProvider.java:32) - Reading AA specific proxy settings
readSettings(AAWinProxySettingProvider.java:37) - The proxy settings key exists in the registry
readSettings(AAWinProxySettingProvider.java:40) - The proxy type value exists in the registry
readSettings(AAWinProxySettingProvider.java:47) - AA proxy type is AUTOMATIC
getProxySelector(AAProxySearchStrategy.java:64) - AA uses automatic proxy settings

We’re not seeing any rejections on the firewall logs either.

We do use SSL interception with self-signed certs, but that is clearly working in my local machine.

It seems like that is what fails on the bot runner, but I can’t determine why.


Forum|alt.badge.img+6
  • Author
  • Navigator | Tier 3
  • 17 replies
  • March 26, 2025

So I have added a ticket to see if anyone can assist.

However, I’ve been doing more testing and have more info that puzzles me even further.

 

I logged in with my developer account to the botrunner VM.

Running this process as a “private” process works normally. (Same behavior as my laptop)

Running it from the same botrunner VM as a “public” process still fails.

 

I cannot understand why this would be the case.

Meeting with our network admins and checking Microsoft Network Monitor did not reveal anything odd.

We whitelisted ALL inbound and outbound ports for a trial and still no difference.

The public and private tasks are identical as I recently upgraded the packages.


Forum|alt.badge.img+6
  • Author
  • Navigator | Tier 3
  • 17 replies
  • March 26, 2025

One more update for whoever is following.

 

It seems like the public process cannot work if I have the process flow checked out.

The public version of the process fails.

I then have to check in the process even though no changes were made.

If I cancel the checkout, this causes things to break.

 

It seems that even if I don’t make any changes, I must perform an actual check-in to the process item or the whole thing breaks.


Lu.Hunnicutt
Pathfinder Community Team
Forum|alt.badge.img+11
  • Pathfinder Community Team
  • 66 replies
  • March 26, 2025

hmm. ​@Aaron.Gleason  ​@Shreya.Kumar ​@Matt.Stewart ​

Any idea why this is happening this way or a way around it?


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • 539 replies
  • March 27, 2025

This needs a support ticket.


Forum|alt.badge.img+6
  • Author
  • Navigator | Tier 3
  • 17 replies
  • March 27, 2025

@Aaron.Gleason I had entered ticket number 02197673 if you are able to check this.

Initially I thought it was network related, but before I could meet with a support member, I figured out a resolution for my immediate issue.

 


Aaron.Gleason
Automation Anywhere Team
Forum|alt.badge.img+10
  • Automation Anywhere Team
  • 539 replies
  • March 27, 2025

@sleemand Do you mind sharing the resolution? Or was this just a workaround?


Forum|alt.badge.img+6
  • Author
  • Navigator | Tier 3
  • 17 replies
  • March 27, 2025

@Aaron.Gleason 

I just finished with my support person and it sounds like this was caused by a known issue that will be fixed in v36

 

Issue steps:

  1. check out the process
  2. run the ‘public’ version
  3. Failure

My steps for resolution:

  1. check in the process as a new version
    1. Must use the check in, cancelling the checkout will cause failures still
  2. run the public version
  3. Success

For now, we won’t be doing any development on the process, so I can keep it checked in.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings