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

Error messages should be better #18

Open
struan opened this issue Apr 26, 2018 · 1 comment
Open

Error messages should be better #18

struan opened this issue Apr 26, 2018 · 1 comment

Comments

@struan
Copy link
Member

struan commented Apr 26, 2018

The error messages that get fed back from the open311 adapter to the scripts calling it are very brief and don't seem to include the details, only the error code. We should include details of the error.

E.g. for the Salesforce one if the credentials have expired it only returns request failed: 500 Internal Server Error which does not help to diagnose the problem.

@struan struan changed the title Better error messages Error messages should be better Apr 26, 2018
@dracos
Copy link
Member

dracos commented Apr 1, 2021

I think this is up to the integration what it dies with - the SalesForce integration only outputs the status line unless the content JSON is an array whose first element contains errorCode, in which case it uses that. Perhaps it could include the full content, whatever it may be, or add a logger->error line if it's an error, instead of the logger->debug one always.

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

2 participants