GET STARTED

Any odata filter on dates fields gives error 500

Pinned Gathering Feedback

Comments

4 comments

  • Avatar
    Maxim (Andarth) Shestakov

    Hi Iara!

    Thank you for your message and my apologies for the issues you are experiencing.
    I am forwarding your ticket and the information you provided to our technical team. We will post an update as soon as we will have details on it

    Regards,
    Maxim

    0
    Comment actions Permalink
  • Avatar
    Maxim (Andarth) Shestakov

    Hi!

    Our team checked and confirmed that there is a floating-issue with the Date filter.
    Currently, it should work fine, but as the root cause is not fixed yet - it might appear in the future, so I've added a task to our backlog to investigate and fix it in future releases.
    Could you please check if it is working now on your side?

    Regards,
    Maxim

    0
    Comment actions Permalink
  • Avatar
    Iara Rodrigues

    Hi Maxim,

    Thanks for the answer. Still have the same problem in all requests in dates.

    I noticied that any request with any filter (not just dates) that can't get a fast response get the error 500. About 30s (used postman for the test).

    If I use any filter that matches any register from 2013 works, but if just exists in a more recent date gives the error.

     

    0
    Comment actions Permalink
  • Avatar
    Maxim (Andarth) Shestakov

    Hi Iara!

    Could you please provide your DevOps organization name so we could check it further? If you do not want to post it publicly, please sent us an email at support@7pace.com

    Regards,
    Maxim

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk