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
Apparently Genesys topic subscriptions can fail in a few different ways. It is not clear what exactly differentiates them from other errors? Also, what is the difference of failure and error; does it matter? See https://github.com/koodaamo/genesys-notifications/blob/main/src/genesys_notifications/channel.py#L138-L148.
Also, 404 responses should be distinguished from one another; see https://github.com/koodaamo/genesys-notifications/blob/main/src/genesys_notifications/channel.py#L104-L111
The REASON.Ambiguous exception reason should then be removed as soon as it's no longer necessary.
REASON.Ambiguous
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Apparently Genesys topic subscriptions can fail in a few different ways. It is not clear what exactly differentiates them from other errors? Also, what is the difference of failure and error; does it matter? See https://github.com/koodaamo/genesys-notifications/blob/main/src/genesys_notifications/channel.py#L138-L148.
Also, 404 responses should be distinguished from one another; see https://github.com/koodaamo/genesys-notifications/blob/main/src/genesys_notifications/channel.py#L104-L111
The
REASON.Ambiguous
exception reason should then be removed as soon as it's no longer necessary.The text was updated successfully, but these errors were encountered: