-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
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
Connection limit and Created new Failed Manifest #197
Comments
Hello, The failureTopicArn should be being used to send notifications in this case. Does anything appear in the logs to this effect? For automatic reprocessing, there is an additional Lambda function in the project which can be hooked up to the failure SNS topic and handles a few different scenarios. Ian |
@IanMeyers not in this case, I have the code copy from 11/10/2018 could be that there was an issue/bug at that time that is not working? The only thing that appear in the logs is the text I put above, for some reason the sns is not called. (I have failureTopicArn in the configuration) Here is some related code of that call that currently I have:
|
Hi, I have two kind of errors:
How I can make a way to reprocess automatically (not manually)?
I have the failureTopicARN but for this kind of error is not called right?
and I have the failedManifestKey that are saved in s3 bucket but the flow ends here.
The text was updated successfully, but these errors were encountered: