Skip to content
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

Catch common client connection errors in ProviderJob #49

Open
uphlewis opened this issue Feb 19, 2024 · 0 comments
Open

Catch common client connection errors in ProviderJob #49

uphlewis opened this issue Feb 19, 2024 · 0 comments
Milestone

Comments

@uphlewis
Copy link
Contributor

Currently if these bubble up from the provider code they are rendered as a "Critical provision provider error" but we can probably add handling to wrap common client connection/timeout/ssl errors and render a friendlier and more helpful error message like "Provider API connection failed".

Examples of errors we could try and wrap:

  • cURL connection errors
  • Guzzle connection errors
  • SSL errors
  • Socket timeouts
  • SOAP connection errors?
@uphlewis uphlewis added this to the v5.0 milestone Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant