Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Physicsman last won the day on October 2

Physicsman had the most liked content!


About Physicsman

  • Rank

Profile Information

  • Gender
  • Location
    London, Great Britain

Recent Profile Visitors

1,248 profile views
  1. Issues with barhistory

    Hello, Based on the session, we checked the logs and narrowed down the calls made from that evening at the time in question.We see five calls made and those were serviced by both of our data centres. Specifically, 4 calls were serviced from DC1 and 1 call was serviced by DC2. Do you recall if the 5 bar result was the more frequent event or was the 200 bar response more frequent? Unfortunately we neither capture responses sent to clients nor any metadata regarding the response so we cannot determine that from our end. If you saw 5 results only once, that could be a problem with the data in DC2, and vice versa. If we can establish some of these additional facts, we can investigate further. Kind Regards, PM
  2. Issues with barhistory

    Thank you for the additional information. Passing it to the team for tuerh investigation. Will update here when I have more information. Kind Regards, PM
  3. Issues with barhistory

    Hi Ken, I just want to follow up on what you wrote here: Do you mean that in your testing on Sunday night, you sometimes received the full 200 bars and sometimes you only received 5? I've tried repeatedly sending the call about 20 times, and every time I receive the full lot as expected. I've not been able to reproduce the error you observed even once. Did you notice any pattern as to when you received the full data and when you did not? As a side note, the following probably is not the cause but I did notice that in the Postman screenshot you are adding your authentication information in the call Parameters. They should be in the call Headers and not in the Parameters. Kind Regards, PM