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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
Currently, if an SQS message fetch fails (e.g. due to a dropped connection) it is reported as an error when it should really be a warning given it will retry on the next poll interval.
A note for the community
Problem
Currently, if an SQS message fetch fails (e.g. due to a dropped connection) it is reported as an error when it should really be a warning given it will retry on the next poll interval.
Configuration
No response
Version
vector v0.23.0
Debug Output
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: