FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    After system reindex patching a user still returns SearchEngineRequestFailedException

    Scheduled Pinned Locked Moved
    General Discussion
    elasticsearch fusionauth error
    3
    3
    3.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      grisha
      last edited by

      We have recently encountered an issue with the SearchEngineRequestFailedException error from the SDK when attempting to patch certain user data. As suggested in this thread, we performed a reindex which resolved the issue for most users. However, some users are still experiencing the error. We would greatly appreciate any assistance in debugging and resolving this issue. The complete error message is as follows: {“generalErrors”:[{“code”:“[SearchEngineRequestFailedException]“,”message”:“A request to the search index has failed. This error is unexpected. Please review the troubleshooting guide found in the documentation for assistance and the available support channels.“}]}.

      danD 1 Reply Last reply Reply Quote 1
      • danD
        dan @grisha
        last edited by

        @grisha Are you seeing any other error messages from FusionAuth or Elasticsearch? Where is your FusionAuth instance hosted (self or in FusionAuth Cloud)?

        --
        FusionAuth - Auth for devs, built by devs.
        https://fusionauth.io

        1 Reply Last reply Reply Quote 0
        • C
          croverw.norene8
          last edited by

          If a user is still receiving a SearchEngineRequestFailedException after a system reindex and patching, there could be several reasons for this.

          Firstly, the issue may not have been related to the index or patching, but rather a problem with the user's search query or the way they are interacting with the system.

          Alternatively, it could be that the reindex and patching process did not fully resolve the underlying issue, and further investigation or troubleshooting is necessary.

          It's also possible that there are other technical or environmental factors at play that are causing the exception to continue occurring. In any case, it may be necessary to consult with technical support or seek out additional resources to diagnose and resolve the issue.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post