Resource Conflicts
What happens when a Schedule Request overlaps with an existing booking.
If your request overlaps with an existing booking on the same resource, or asks for more of a limited resource than is available, FMX flags it as a conflict rather than blocking your request outright.
Two kinds of conflicts
- Time overlap — another request already has the same resource booked during some or all of your requested time.
- Quantity overlap — for resources tracked by quantity (like a shared set of tables), your request would push the total booked past what's available across your own request's occurrences.
Resolving a conflict
When a conflict is flagged, you have two options, depending on what your organization allows:
- Exclude the conflicting occurrence — remove just the overlapping part of your request rather than the whole thing.
- Include it anyway — proceed with the overlap, if your organization permits booking through conflicts.
Conflicts are only flagged, not automatically rejected — nothing is decided for you.
A worked example
Say two people both try to book the main conference room for an overlapping hour. The second request is flagged as a time conflict at submission. That person can either exclude the conflicting occurrence and pick a different time, or — if their organization allows it — submit anyway and let both requests stand, with the conflict left visible to whoever manages that room.