TimeTracker API returning "500 Internal Server Error"

Officially Answered

Follow

New post

Douglas Lindsay

• February 18, 2020 14:54

Hello, I have a number of reports that pull in data from the TimeTracker API. Today they are reporting a 500 internal server error from the API. Can you advise? Thanks.

0

• 

  Maxim Shestakov

  • February 18, 2020 15:10

  Hi Douglas!

  Thank you for your message and my apologies for the issues you are experiencing.
  We need more details to help you, so I've created a support ticket for you.

  Regards,
  Maxim

  0

  Comment actions Permalink
• 

  Douglas Lindsay

  • February 19, 2020 09:09

  Apologies; this was a false alarm. I discovered I had somehow changed directory on Azure and that resulted both in authorization failures for the Timetracker plugin, and also in your server returning "500 internal server error" responses when my Powerquery reports tried to execute against your API.

  Could I suggest that your error messages might benefit from a review, to respond with something indicating the possible reasons for the error rather than reporting internal server error?

  Many thanks!

  0

  Comment actions Permalink
• 

  Maxim Shestakov

  • February 19, 2020 14:28

  >Could I suggest that your error messages might benefit from a review, to respond with something indicating the possible reasons for the error rather than reporting internal server error?

  Sure, I've created an item to improve this message in our further releases

  Regards,
  Maxim

   

  0

  Comment actions Permalink

Please sign in to leave a comment.