Replies: 2 comments
-
Closing this as a duplicate so we can continue tracking the discussion in this issue: #8062 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
while running below AWS CLI command and its invoking lambda to trigger EMR step. AWS cli getting network error after 3 min and its triggering lambda again. due to this we are not getting proper logs/response from aws cli.
aws lambda invoke --debug --cli-read-timeout 0 --cli-connect-timeout 0 --function-name autosys-job-execution-lambda --region us-east-1 --cli-binary-format raw-in-base64-out --payload "{"env":"UAT","profile":"hrcore","jobType":"conformed","process":"scalaclassprocess","mode": "ONETIME"}"
error message:
Network Error
A communication error occurred: ""
Beta Was this translation helpful? Give feedback.
All reactions