← Back to Help

Event troubleshooting

Diagnose RSVP, upload, visibility, and results access issues quickly.

Event troubleshooting

Use this page when riders report “it’s not working”.

Rider cannot RSVP

Check, in this order:

  1. Is the rider logged in?
  2. Is event status allowing normal join flow?
  3. Are entries already closed?
  4. Does Who can join permit this user?
  5. If club event: is user a member, or are non-member invites enabled?
  6. If invite-only flow: was the correct invite link used?

Rider can view but cannot join

This usually means read-only preview is working, but join permissions are still restricted by access policy.

Common causes:

  • rider is not logged in
  • rider has invite preview rights but not join rights
  • club event does not allow non-member invite joining

For club non-public events, enable non-member invite admission only when intended.

This is expected when anonymous preview is not allowed for that event policy.

Preview before login is typically available for:

  • listed public events
  • valid invite-link flows

If neither applies, login is required first.

Rider cannot upload activity

Most common cause: event is not active.

Uploads/linking are blocked outside active lifecycle state.

Also check:

  • rider is marked going
  • rider has required slot/wave assignment when applicable

Event not appearing in lists

Check discovery settings:

  • unlisted events do not appear in normal feed/search
  • archived events are hidden from normal discovery
  • follower/member-scoped discovery limits visibility

Results not visible to a user

Check results visibility first:

  • participants-only means host/admin + going participants
  • interested status does not grant participant-only result access

Host action confusion

If host says “I published but riders can’t join”:

  • publishing results finalizes standings; it is not the same as opening entries

If host says “I cancelled by mistake”:

  • cancelled and archived are separate states; choose carefully in admin actions

Fast incident checklist for host/admin

When something breaks during an event:

  1. Confirm current lifecycle status.
  2. Confirm user role (host/admin/member/non-member/participant).
  3. Confirm access + invite settings.
  4. Confirm discovery/results settings.
  5. Test once logged out (preview) and once logged in (full actions).

This sequence resolves most support issues quickly.