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

    Cancel a Previously Taken Action

    Scheduled Pinned Locked Moved Solved
    Q&A
    2
    5
    54
    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.
    • D
      d.chinguun.0301
      last edited by

      Hi, I am currently using FusionAuth version 1.53.2. When I try to cancel actions that are in progress using the API, it returns a 404 error. I've read through all the release notes but didn't find any mention of this issue. Is this a known bug, or am I implementing the API call incorrectly?

      mark.robustelliM 1 Reply Last reply Reply Quote 0
      • mark.robustelliM
        mark.robustelli @d.chinguun.0301
        last edited by

        @d-chinguun-0301 can you give us some example code of what you are trying to do? What API are you using and how are you trying to cancel the call?

        D 2 Replies Last reply Reply Quote 0
        • D
          d.chinguun.0301 @mark.robustelli
          last edited by

          Hi @mark-robustelli,

          I initially tried the Take an Action on a User API (https://fusionauth.io/docs/apis/actioning-users#take-an-action-on-a-user) with the following request body:

          {
          "broadcast": true,
          "action": {
          "actioneeUserId": "dd0e31c9-a7cb-3597-bff1-45d3b13255ad",
          "actionerUserId": "dd0e31c9-a7cb-3597-bff1-45d3b13255ad",
          "comment": "This user is being a jerk",
          "emailUser": true,
          "expiry": 1771586483322,
          "userActionId": "dfc52db9-ff76-4606-92b6-c7419ae5fe6c"
          }
          }
          Afterward, I attempted to cancel the action using the Cancel a Previously Taken Action API, but I received a 404 response.

          I used the following actionId:
          dfc52db9-ff76-4606-92b6-c7419ae5fe6c, which does exist.

          Could you help me understand what might be going wrong?

          Thanks!

          1 Reply Last reply Reply Quote 0
          • D
            d.chinguun.0301 @mark.robustelli
            last edited by

            Thanks for your response, @mark-robustelli. Apologies — it was my mistake. I was supposed to use the instance ID of the previously taken action, not the User Action ID.

            mark.robustelliM 1 Reply Last reply Reply Quote 0
            • D d.chinguun.0301 has marked this topic as solved
            • mark.robustelliM
              mark.robustelli @d.chinguun.0301
              last edited by mark.robustelli

              @d-chinguun-0301 No problem. Glad you figured it out. No need for apologies, if you were confused others may be as well. Now when they search here, they will have an answer. Have a great one

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