We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If there's a problem with the job, the GitHub job should fail instead of being marked as succeeded.
Since January 1st, the GitHub repository analytics job is broken. However, the jobs is still marked as "Succeeded".
N/A
Check the output of the Lambda invocation for function errors.
Check the latest logs of the Dispatch Analytics job.
latest
3.7
PyPi
No response
The text was updated successfully, but these errors were encountered:
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Sorry, something went wrong.
This is now released under 2.31.0 version!
rubenfonseca
Successfully merging a pull request may close this issue.
Expected Behaviour
If there's a problem with the job, the GitHub job should fail instead of being marked as succeeded.
Current Behaviour
Since January 1st, the GitHub repository analytics job is broken. However, the jobs is still marked as "Succeeded".
Code snippet
Possible Solution
Check the output of the Lambda invocation for function errors.
Steps to Reproduce
Check the latest logs of the Dispatch Analytics job.
Powertools for AWS Lambda (Python) version
latest
AWS Lambda function runtime
3.7
Packaging format used
PyPi
Debugging logs
No response
The text was updated successfully, but these errors were encountered: