Problems creating or editing events are usually fixed with a few checks. This guide covers the most common issues: events not showing on your calendar widget, recurring events not generating correctly, image upload problems, capacity settings not working as expected, and custom registration fields not saving.
If you created an event but don't see it on your website's calendar widget, work through these checks.
Events must be published to appear on your calendar widget. Draft events remain hidden until you publish them.
Open your event in the Eventually dashboard.
Look at the event status near the title.
If it says Draft, click Publish event to make it live.
By default, calendar widgets show events from the past 6 months through the future. If your event is outside this window, it won't appear.
To show past events or extend the date range, adjust your widget settings in Customization → Widgets. See Set up your calendar widget for details on configuring display filters.
Widgets can filter out sold-out events. If you've enabled "show available only" in your widget settings, events with no remaining capacity won't display. See Set event capacity and ticket limits to check availability.
If your widget is filtered to specific categories, events without matching categories won't show. Make sure your event has at least one category that matches the widget's filter.
Squarespace caches embed blocks. If you just published an event or made changes, the widget may take a few minutes to update. Try:
Hard refresh your browser (Ctrl+Shift+R or Cmd+Shift+R)
Wait 5–10 minutes for the cache to clear
Check the event in the Eventually dashboard to confirm it's published
Recurring events must have an end condition — Eventually doesn't support open-ended series. If your recurring event isn't generating all the sessions you expect, check these settings.
Every recurring event requires one of these:
End after X occurrences — The series stops after a specific number of sessions.
End by date — The series stops after a specific calendar date.
If you don't set an end condition, the series won't save properly. Make sure your schedule includes either an occurrence count or an end date.
If you excluded dates for holidays or breaks, those sessions won't appear. Check your recurring event's date exclusions in the Eventually dashboard to confirm the dates you expect are included.
When you edit a recurring event, you choose how far the changes apply: This event, This and following events, or All events. If you expected changes to apply to future sessions but they didn't, you may have chosen This event instead of a broader scope.
See Creating recurring events for more on edit scopes and managing recurring series.
If a recurring series for an evening event in a US time zone shows sessions one day early, check the event's Time zone first. Recurrence dates are generated in the event's selected time zone for daily, weekly, and monthly schedules.
Cause: Event start times are stored in UTC. For a 5:00 PM Pacific event, that UTC instant is already the next calendar day. Older series may still have been generated from that UTC day for weekday and date math, so sessions can land a day early until the series is saved again.
Fix: New series keep the intended local weekday and date. For an existing series that still looks wrong, open the recurring event, confirm the Time zone is correct, and save it again so sessions regenerate with the current schedule. If dates still look wrong after a save, contact support at [email protected] with the event name and the dates you expect.
Some monthly recurring events that repeat on a specific weekday position (for example, "the first Monday") may fail to publish with a server error if the stored schedule is missing its week position.
Cause: A small number of older or incomplete saved monthly rules were missing the week-position detail required to generate the series. This triggered an error at publish time.
Fix: Re-open the event and click Publish event. The system now derives the week position from the event's start date when the stored value is missing. Events that start on the fifth occurrence of a weekday in the month are treated as Last so the series does not drift into the next month. If you explicitly set a position in the editor, that choice still takes precedence. No data migration is needed.
Cause: Evie only keeps a recurrence rule and generates the series when the prompt clearly describes a repeating pattern and a usable end condition.
Fix: Rewrite the prompt with frequency and end details (for example “every Thursday for 8 weeks”), submit again, or open Edit all the details and enable the recurring schedule in the editor. See Using Evie (AI) to create an event and Creating recurring events.
Cause: Older schedule saves could tear down an existing recurrence rule when the editor echoed the same recurring schedule type back on save.
Fix: Save again with the current product. Saving a schedule that is already recurring keeps the existing rule and child dates. The series is removed only when you switch the event away from a recurring schedule. If dates are still missing after a current save, contact support at [email protected] with the event name.
If you're having trouble adding images to your event, check these limits and error messages.
Event images have these constraints:
Maximum images: 10 per event
Maximum file size: 5 MB per image
Accepted formats: PNG, JPG, WebP, GIF
If you see an error like exceeds 5MB limit or Events can have at most 10 images, you've hit one of these caps.
The message unsupported type means the file isn't in an accepted format. Convert your image to PNG, JPG, WebP, or GIF before uploading.
If images uploaded successfully but don't appear on your calendar widget:
Make sure the images finished processing — large files take longer
Refresh the page where your widget is embedded
Check that the widget display settings include image previews
For step-by-step upload instructions, see Add multiple images to an event.
If tickets aren't selling out when expected, or capacity numbers seem wrong, check these settings.
Leaving the capacity field blank means unlimited — not zero. If you meant to cap attendance, enter a number in the Total Event Capacity field.
Total Event Capacity: Sets an overall cap for the event across all ticket types
Ticket Limit: Caps a specific ticket type individually
For example: If Total Event Capacity is blank but VIP tickets have a limit of 20, General Admission sells unlimited — only VIP stops at 20.
If you set both Total Event Capacity and per-ticket limits, the more restrictive one wins. A 100-person event with VIP capped at 20 means VIP stops at 20, but General keeps selling until the combined total hits 100.
See Set event capacity and ticket limits for detailed examples.
Each session in a recurring series has its own capacity. If you updated capacity for one session but expected it to change others, check your edit scope — you may have applied it to This event instead of All events or This and following events.
Custom questions for attendees help you collect extra information at checkout. If they're not saving or appearing, check these issues.
Each custom field requires a label — the question or prompt shown to attendees. If you try to save without a label, the field won't persist.
Custom fields support these data types:
Short text — One-line answer
Long text — Multi-line answer
Dropdown — Single selection from a list
Checkbox — Multiple selections from a list, or a single checkbox
Yes / No — Simple toggle
Make sure you selected the right type and added options for dropdown and checkbox fields. For detailed setup instructions, see Custom registration questions and fields.
You don't need to add name or email fields — they're captured automatically for every attendee. The empty state message No custom questions yet. Name and email are always collected. confirms this.
If you change a completed event date to the future, it may leave the Completed tab and reappear in Upcoming. This is expected for single, standalone events.
Eventually automatically marks published single events as Completed once their effective end time passes. When you reschedule a standalone event to a future date and save it, the system restores the event to published automatically so it shows in Upcoming again.
The restore only runs if the event is ready to publish — for example, it has tickets, an external registration URL, or registration disabled. Recurring series events are excluded and keep their original status behavior.
If an event is already stuck in Completed with a future date, open it, adjust the date if needed, and click Save changes. The event will move to the correct tab on its own.
If you see error messages during event creation, check these common issues.
Every event needs a title. Enter a name in the first step of the wizard before continuing.
For single events, set Start at before leaving the details step. For multi-day events, add at least one event date. The wizard won't let you proceed without a date.
This generic error can mean a temporary connection issue or an unexpected validation failure. Try:
Saving as a draft first, then publishing
Refreshing the page and re-entering your changes
Checking for browser console errors (open Developer Tools → Console)
If you've worked through these checks and still can't create or edit your event, reach out to Eventually support at [email protected]. Include:
The event name and status (draft/published)
What you were trying to do (create new, edit existing, add images, set capacity, etc.)
The exact error message you saw
Screenshots if possible
Creating an event with the 4-step wizard — Step-by-step event creation
Creating recurring events — Set up repeating schedules and manage sessions
Date, time, timezone, and location autocomplete — Confirm the time zone used for display and recurring dates
Set event capacity and ticket limits — Configure seat limits and sold-out behavior
