Troubleshoot Events
Recover from missing events, refused saves, access errors, registration-state issues, and attendee invitation failures.
Identify whether the problem is publication, authorization, attendee state, or a display setting before changing the event.
The event is missing from Upcoming events
- Open the event through Manage events.
- Check Status on Details.
- Use Published when the event should be listed. Hidden remains direct-link only, and Draft is manager-only.
- Check its date mode. An exact-date event moves to Past events after its configured end time.
- Confirm the organization owns or co-hosts the event shown in the current list.
The event form will not save
When the page says Fix the highlighted fields, follow the page to the first error and complete every required field. Exact-date events require start time, end time, and timezone. Other date modes require their displayed date fields.
If the URL slug is rejected, another event or a retained redirect in the same organization already uses it. Choose a different stable slug and save again.
Manage events redirects to the public page
The flash You are not authorized to access this page on /{organization-slug}/manage means the current user has no manageable event anywhere. The organization slug in that URL does not limit the management list.
- Organization members can manage their organization’s events.
- Direct managers can manage only assigned events.
- Event creation and manager assignment require organization membership.
An administrative route for one event redirects separately when the current user cannot manage that requested event. Ask an organization member to add the correct membership or direct manager assignment. Do not work around either route guard with a shared link.
Manage events shows no matches
No manageable events found appears after an authorized user reaches Manage events but the current search or filters leave no matching rows. Clear the search and filters. If the route redirects to the public page instead, resolve the missing organization membership or direct manager assignment described above.
A visitor cannot see the venue, agenda, or attendee list
Check the corresponding event setting and the visitor’s registration state:
- Show location to may require an Accepted registration.
- Show agenda page may be limited to confirmed attendees.
- Show attendance list? may be limited to accepted attendees or disabled.
- Speakers and gallery have separate page toggles.
Changing an attendee to Accepted can reveal gated information. Make that decision only when the registration should actually be accepted.
Registration is still waiting
Waiting for confirmation from the host. covers both Pending and Under evaluation registrations. In Attendees, inspect Status and Assigned to. Accept or reject a Pending record, or let the assigned evaluator complete an Under evaluation record.
If a previously rejected person should be reconsidered, use Status reset or another deliberate manager action. The rejected attendee has no self-service reapply control.
Registration appears open after the signup target
This is expected. Signup target is marked For internal measuring. and does not enforce capacity. Review registrations in Attendees and communicate decisions explicitly.
Registration or invitations are unavailable
- An exact-date event disables registration and invitation sending after its end time. The invitation panel may still open with This event is already over. You can no longer invite friends to join. in place of the form.
- Registration requires sign-in.
- Invite a friend also requires the event’s invitation policy to admit the current user.
- A TBA event is not treated as ended automatically. Update its date and publication state deliberately when plans change.
An invitation fails
- Complete First name, Last name, and a valid Email for every row.
- The panel lets you queue up to 10 invitees in one submission.
- You have already invited this person to the event. means the same sender already used that email for this event.
- Invalid or incomplete names and email addresses show inline field errors. Correct those rows before submitting again.
- Please check the forms for errors before submitting. is the fallback when an otherwise valid multi-invite submission could not be stored. Keep the panel open, inspect every row, and retry only after confirming the intended recipients.
- Invitations were successfully sent. confirms that the invitation rows were stored and delivery was attempted; it does not prove mailbox receipt. Inspect Previous invitations before leaving the panel.
A Meet status or invitation changed while the page was open
The attendee action rechecks the current profile and registration before sending:
- {name} is already on Meet means the attendee completed a profile after the row rendered. No invitation is sent; reload the row and expect On Meet.
- {name} is no longer attending, so no invite was sent means the registration changed to Rejected or Cancelled before the click completed. Review the registration instead of retrying.
- Could not invite {name} to Meet can mean delivery failed or that Events could not record the timestamp after delivery. An unchanged time does not prove no email was sent. Reload, confirm with the recipient before retrying, and avoid sending a duplicate.
After a recorded first invitation, the action becomes Send the Meet invite again. There is no cooldown and the column keeps only the latest recorded time, not an invitation history. Confirm the recipient and relative time before resending. The Meet column has no filter, and these invitations do not create an Event messaging logs entry.
The manager must be an owning-organization member or direct manager of the requested Event. A copied attendee ID from another Event cannot be used through this route. The manager’s own Meet profile state does not grant Events access.
An event update was saved but no email was sent
Venue or timing edits are saved before Notify attendees about changes? appears. Choosing No, don't send notifications keeps the update without email. Check Event messaging logs for an Event change notification when an email should have been sent.