Inconsistent results with recordedTimePeriods endpoint

Answered

Comments

3 comments

  • Avatar
    Ichiro

    Hi Daniel Reichman, Ph.D.,

    Thanks for your question, can you show us the result of your API response?
    Do you mean if you request twice or more times, then the response will become normal?

     

    Since the Nx v6.0 has been release, can you try the new API endpoint - GET /rest/v3/devices/*/footage?
    (https://meta.nxvms.com/doc/developers/api-tool/rest-v3-devices--footage-get?type=1&system=17)

     

    0
    Comment actions Permalink
  • Avatar
    Daniel Reichman, Ph.D.

    It's intermittent and hard to replicate, that's been the issue. we have been integrated with Nx for like 4 years and it only happens periodically.

    And yes, it's that we make the call once and we get the full results set, then one hour later we make a call and the results set is empty. Then the next hour we get the full results set.

    We can look into the v3 api but is this a known issue?

    0
    Comment actions Permalink
  • Avatar
    Ichiro

    Hi Daniel Reichman, Ph.D.

    I haven’t observed the same behavior and would caution against drawing conclusions from the limited information available. Typically, issues like this can be related to server performance, or in some cases, corrupted database or index files. But without further log or environment detail, we may not be able to provide the answer.

    If possible, I would recommend providing the server application's debug logs, and if needed, we may also need the remote access to your system for a more thorough investigation.

    Additionally, since Gen6 has been released, the API has shifted to a different format and endpoints. Any potential fixes would need to be based on this new structure. If you are seeing the same issue on Gen6 and the v3 API, we can certainly investigate further using the latest code base.

    Thanks.

    0
    Comment actions Permalink

Please sign in to leave a comment.