Getting error 422 instead 404 for Rotation API calls

XMLWordPrintable

    • Severity 3 - Minor

      Issue Summary

      Hello team, Noticed a (422Unprocessable Entity) error when querying the Schedule Rotation API request. This is in continuation with the issue discussed in the support request https://jira.atlassian.com/browse/OPSGENIE-860

      This is reproducible on Data Center: (yes) / (no)
      Yes

      Steps to Reproduce

      1. Create a rotation with https://api.opsgenie.com/v2/schedules/:scheduleIdentifier/rotations POST request.
      2. Once the rotation is created with a specific name and we send the same request again to create another rotation with the same name we are getting below error.
      422 Unprocessable Entity"

      {
          "message": "Cannot add/update Schedule with name [Rota22]. There is already one ScheduleRotation with same name.",
          "took": 0.065,
          "requestId": "6ff3e8f8-0f0b-4d26-a3c9-9efe055a24de"
      }
      

      Expected Results

      NA

      Actual Results

      Getting 422Unprocessable Entity error

      Workaround

      NA

            Assignee:
            btezergil
            Reporter:
            Mubeen Mohammed
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: