Monitor Stop

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • avc859587618170
    Brainiac
    • Jun 2024
    • 65

    Monitor Stop

    Hey gang.. I think I may not be calling the Monitor Stop endpoint correctly. I always get a 500 Internal server error response. I'm posting to "fe/v1/MonitorStop" with this payload:

    Code:
    {
        "monitorCrossRefID": "90"
    }
    I get a 500 Internal server response with this payload:

    Code:
    {
        "MonitorStopResponse": ""
    }​
    Does that seem right?

    Thanks!!

    Dave
    Dave Morrison
    Software Engineer
  • flynn1
    Brainiac
    .
    • Jun 2011
    • 82

    #2
    Yeah, I see that too. The monitor is actually stopped but the WTI module is barfing when generating the response. I have reported this as AES-34188.

    Martin

    Comment

    • avc859587618170
      Brainiac
      • Jun 2024
      • 65

      #3
      Awesome!! Thanks Martin!

      Dave
      Dave Morrison
      Software Engineer

      Comment

      Loading