Unable to edit or delete an event in a team calendar

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      Sometimes site admin or calendar owner unable to edit or delete certain event from team calendar in the confluence space. The error message displayed is 'Something went wrong. Please try again later.'

      Steps to Reproduce

      1. Navigate to the team calendar in the Confluence space at https://<domain>.atlassian.net/wiki/spaces/<SPACEKEY>/calendars.
      2. Attempt to edit or delete the event.
      3. Observe the error message: 'Something went wrong. Please try again later.'

      Expected Results

      The event should be deleted

      Actual Results

      The event doesn't delete and the following error message is displayed on the user interface:  Something went wrong. Please try again later.'

      In HAR logs we can observe following error:

      • Request URL: https://utas.atlassian.net/cgraphql?q=DeleteSubCalendarEvent
        Request Method:POST
        Status Code: 200 OK
        Remote Address: 13.35.248.5:443 
      • [
            {
                "data": {
                    "confluence_deleteSubCalendarEvent": {
                        "success": false,
                        "errors": [
                            {
                                "message": "calendar3.error.deleteevents.notexist",
                                "extensions": [],
                                "__typename": "MutationError"
                            }
                        ],
                        "__typename": "ConfluenceDeleteSubCalendarEventPayload"
                    }
                }
            }
        ]  

      Workaround

      • Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              James Broe
              Reporter:
              Shahid Qureshi (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: