Document Extraction: Extract Data not working

​@Srini 6969 Your only way of knowing what’s going on in the PROD environment is to look at the Bot Agent logs on the bot runner.

Have you confirmed the packages are up to date?

When you promote your bot, are you making sure the package version is the same in PROD as it is in DEV?

Might be something to look at.

Hi ​@Aaron.Gleason : Thanks for the reply.

These are the two errors I can see in the logs after i enabled the Trace. Any idea where the issue is???

ERROR [aaiextraction.common.fm.gateway.connector.get_oem_gateway_auth_credential:41] DA: Gateway Connection failed! HTTPSConnectionPool(host='xxxxxxxxxxautomationanywhere.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)')))

 TRACE [BotRunner-2f412cd1-86e1-4c2b-adbb-5d7d3ed2bcbb_ecb341a2e5aafbd8] - com.automationanywhere.synchronous.messenger.MessengerProtocol {CORRELATION_ID=2f412cd1-86e1-4c2b-adbb-5d7d3ed2bcbb_ecb341a2e5aafbd8, deploymentId=2f412cd1-86e1-4c2b-adbb-5d7d3ed2bcbb_ecb341a2e5aafbd8, traceId=ecb341a2e5aafbd8} - getProcessOutput(TextMessengerProtocol.java:130) - Process id:1628 output: #output_start#{"metadata": {"documentId": "F1FABC2F-062D-42F5-8DBC-EA2187231A67", "filepath": "", "executionStatus": {"statusCode": 500, "statusMessage": "DOCUMENT_FAILED", "message": "Gateway connection error! Check bot logs for more details on this error."}, "timeInMs": 0.18179750442504883}}#output_end#

Hi ​@SNorris : Yes the packages are same in DEV and PROD. Thanks.

​@Srini 6969 Excellent sleuthing. The message is saying there is an SSL error on the server side. If this is working on the DEV machines but not the PROD, I would say this could be an issue with a proxy server, firewall, or gateway server that the PROD machine is behind but the DEV machine is not. 

Unfortunately, there are systems, like Netskope, that use man-in-the-middle SSL key spoofing to be able to inspect your SSL traffic. If the key spoofing isn't done properly (and I use the word "properly" quite loosely), an SSL error could appear like this. 

Check with your IT department and see if they are using one of these tools and whether or not it can be disabled for your PROD machines.