Skip to main content
Support Documentation

How to Review an Event Conflict Reason

  • July 18, 2025
  • October 7, 2025 at 10:07 PM
  • 0 replies
  • 217 views

Forum|alt.badge.img

When the provider event is synced to Appspace, an event within Appspace might be set as conflict/canceled due to conflict. This may be caused by one of the reasons below:

  1. Conflict with existing events in Appspace
  2. Constraint violation
  3. Google Calendar (GCAL) room only: Room event declined from GCAL room

 

If the event is canceled due to conflict, unfortunately our current product design is unable to show the conflict reason from the user interface (UI); for example:

 

Troubleshooting Steps

Steps to manually check the conflict/cancellation reason:

  1. Log into the Appspace admin console.
  2. Navigate to the reservations module.
  3. Open your browser developer tools and select the network tab (select F12).
  4. Select the event.
  5. There should be a GET API in the network tab similar to: e53472b6-9d04-4ce9-9dfe-fb53f826598b?includesourceobject=true.
  6. Select this value, and select the preview tab.
  7. Search for the reservableResults value.

We can determine what the reason is that the event is in conflict based on the data from reservableResults:

  1. If constraintValidationResult is visible, the reservation is in violation of a constraint rule. 
  2. If events is visible, the reservation is conflicting with (an) existing event(s) in Appspace in terms of event time.
  3. If unavailableReason is visible and includes ProviderResourceDecline, this tells us that the GCAL room declined the event in GCAL.

The room declined the event in GCAL (This is GCAL only)

When the room declines the event in GCAL, we sync the provider event, and we know that the room is declined. In this case, when syncing to Appspace space reservation, we will either set the event status as conflict/canceled based on the provider reservations with conflicts setting within the admin console > reservations > settings.

In this case, the user is not able to view the reason for the conflict/cancellation, as this is not currently supported by the Appspace console user interface (UI).