"failed GET request to scribe" error when fetching the departments

5 Comments

  • Greg - Community Manager
    Comment actions Permalink

    Hi Radu! Out of curiosity, did this occur around 07:17 UTC today? If not, could you share the time that it did occur so that I can dig into this a bit further? Unfortunately, that particular error response can be returned for both client (4xx) and server side (5xx) errors, so timing will help here.

     

    0
  • Radu Unknown
    Comment actions Permalink

    Hi Greg. This particular log is from 1st-Mar-2021 21:00 UTC. We got the error multiple times in the span of ~90 minutes. I can't tell anything about today as the bot was not running.

    0
  • Greg - Community Manager
    Comment actions Permalink

    Thanks for that Radu. I do see a spike of server errors for the Conversations API on our side between 21:34:38 and 21:35:15 on March 1, with a few incidental spikes around that. I would feel fairly confident that these issues were related to that, however it is difficult to say for certain. Do you have any other timeframes when these issues have occurred so that I can see if there is a correlation?

    0
  • Radu Unknown
    Comment actions Permalink

    Hi Greg,

    I don't have other timeframes as the bot was stopped in order to investigate these issues.

    Shouldn't these spikes of server errors for the Conversations API on your side already raise some concerns and have some internal tests/investigations/fixes done?

    Thanks,

    Radu

    0
  • Greg - Community Manager
    Comment actions Permalink

    Yes, they certainly would and did, which is why we saw brief spikes and then corrections. Have you continued to see any problems in this area?

    0

Please sign in to leave a comment.

Powered by Zendesk