Two kinds of problem
The agenda checks itself on every change. It knows two kinds of problem:
- A conflict is a hard error, and the grid refuses the change that would cause it. For example: the same person in two places at the same time.
- A warning points to something you may want to change, but the grid allows it. For example: two sessions on the same topic at the same time.
What the grid refuses, and what it asks
The grid refuses a change that would put:
- the same person in two places at once, including a chair whose block runs at the same time;
- a session in a room that does not suit its presentation type, for example an in-person session in an online room;
- a session outside the agenda's days or hours.
When you drop a session onto a place that is already taken in that room, the grid asks what you want, in Agenda conflict: Swap places, Replace it (the session that was there goes back to the list), or Shrink to fit.
When you place a session outside the times a speaker said they are available, the grid asks for a Note in Outside availability, and then places it anyway.
Step 1: Open the Issues panel
In the Agenda Builder's menu, under Check, open Issues. It lists every conflict and warning as a sentence that names the entries and the people concerned.
Step 2: Work through each issue
On each issue:
- Show takes the grid to the place.
- Explain says what the rule checks and what clears the issue.
- Fix with Amal asks Amal, the AI assistant of run.events, for a fix. A fix that moves entries comes back as a proposal, which you accept or reject.
- Acknowledge… and Dismiss set aside a warning you accept as it is.
To work through the people with problems first, open Filters and choose Speakers with issues.
Step 3: Set the rules to your congress
In the menu, under Tools, open Agenda Settings and its tab Rules. It switches each warning on or off and shows how many warnings each rule marks now. Some rules take a threshold, for example how many minutes a room may stand empty between two entries.
Typical warnings you may meet:
- a person's sessions too close together;
- sessions with the same label at the same time;
- more people expected than the room seats;
- a presenter who has not confirmed;
- a room empty for too long between two entries;
- a deck that is not ready;
- numbers that no longer follow the schedule.
What the warnings do not catch
- A room empty for a whole day, or before its first entry, is not flagged; the empty-room warning counts only gaps between two entries.
- More people than seats is checked only for rooms with a Capacity, and only from what attendees have marked as favourites or the tickets linked to sessions.
- Same label at the same time reads every shared label, not only topics, so an internal label can raise it too.
Good to know: no warning stops a publication. Before you publish, look at the warnings once more, and dismiss those you accept, so that the list stays useful for the next round of changes.
Related articles