TimeTracker API returning "500 Internal Server Error"

Officially Answered

Comments

3 comments

  • Avatar
    Maxim (Andarth) Shestakov

    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
  • Avatar
    Douglas Lindsay

    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
  • Avatar
    Maxim (Andarth) Shestakov

    >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.

Powered by Zendesk