Post

2 followers Follow
0
Avatar

Error Messages should have more information

 

Jason Ray

May 17, 10:24 PDT

There are many instances of system errors occurring (and often being logged) where the error messages and logs do not contain enough information to determine what is happening or what needs to be done to correct the error.

We are experiencing some errors in API calls like this:

API call response message:
"5/10/2019 10:01 AM Unable to update record in CLZ: Body:[],"

The Body of the error is blank and there is no way to determine why the update failed.

For Clarizen rules, when a rule runs and a referenced object is bad (or has been deleted) the error and log messages do not contain any information about the "bad" object. An Object ID, external or normal, or whatever other information is available is needed to debug.

You should improve the feedback on errors so that they can be properly resolved.

Jason Ray Not planned

Official comment

Avatar

Hi Jason,

The response example in your question does not look like original response from Clarizen API. We never response with "CLZ:". Is it possible that you use some intermediate tool for Clarizen API?

In addition, can you, please, give us some request examples that produce such responses? It will help us to understand and improve messages.

Thanks.

Alex Broitman

Please sign in to leave a comment.

5 comments

0
Avatar

Alex:  The API example is from a call from our Salesforce instance, we are looking for more examples and to see if Salesforce is impacting the error messages.

The issue with deleted objects inside Clarizen itself, however, is a separate issue :-)

Thanks

Jason Ray 0 votes
0
Avatar

Alex:

I spoke with our Salesforce deveoper, and he provided the screenshot of the code below.  The error message is his lead (Unable to update record in CLZ :) followed by the response message he received from Clarizen, which is empty.  He may be making an error here as well - please let me know if this helps better identify the issue with the API responses.

Jason Ray 0 votes
0
Avatar

Hi Jason,

It is very difficult for me to understand your case. Usually we answer with meaningful body which includes "referenceId". This "referenceId" help us to identify the error and find it in our internal logs.

In your case you say that the body is empty. I can hardly believe it. Can you send me please the exact request that you send to Clarizen API? I will try to reproduce the error. You may have to open a support ticket for this.

 

Alex Broitman 0 votes
0
Avatar

I will request the details and respond as soon as they are available.  Thanks for the quick reply!

Jason Ray 0 votes