You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a request is sent for CDR from the Lambda function, the code will only trigger if the response is 201 or 500.
If the response is a 206 it just drops the message. This causes issues with partially processed archives.
I haven't been able to replicate a 400, but since I got a 404 in the CloudWatch logs, I assume it handles 400 codes also.
One thing to keep in mind is that unsupported files also return a 206 but since we are sending a request with NoAnalysisReport, the response body wont have anyhting to download.
Actual behaviour
206 responses are dropped from the lambda function and nothing is logged
Expected behaviour
Response with 206 and a response body to download should be handled from function. Archives partial processed should be present in processed bucket
The text was updated successfully, but these errors were encountered:
After a request is sent for CDR from the Lambda function, the code will only trigger if the response is 201 or 500.
If the response is a 206 it just drops the message. This causes issues with partially processed archives.
I haven't been able to replicate a 400, but since I got a 404 in the CloudWatch logs, I assume it handles 400 codes also.
One thing to keep in mind is that unsupported files also return a 206 but since we are sending a request with NoAnalysisReport, the response body wont have anyhting to download.
Actual behaviour
206 responses are dropped from the lambda function and nothing is logged
Expected behaviour
Response with 206 and a response body to download should be handled from function. Archives partial processed should be present in processed bucket
The text was updated successfully, but these errors were encountered: