Skip to content
English
More support
Log into SimpleEvents Dashboard
  • There are no suggestions because the search field is empty.

Error Reference: Fixing Event Creation and Editing Errors

Match the message you're seeing to the section below. Most event creation and editing errors trace back to one of three causes: an expired HubSpot connection, missing permissions (scopes), or a HubSpot-side outage.

"There was an error processing your request on HubSpot's end. Please try again later."

SimpleEvents called HubSpot's API and HubSpot returned an error. In order of likelihood:

  1. Wait 15 minutes and retry. HubSpot has intermittent API incidents; these resolve on their own. Check the banner at the top of your SimpleEvents dashboard — if we know about an outage, it's posted there.
  2. Reconnect HubSpot from Settings if the retry fails: How to reconnect your HubSpot account.
  3. If it persists beyond an hour, contact support with your Event ID and the exact time you tried.
"Your HubSpot Account is missing some key properties. You need to reconnect your HubSpot Account. — error code: 400"

SimpleEvents expects certain custom properties on your HubSpot portal and can't find them (they may have been deleted, or the connection was made before a newer feature added them). Fix: reconnect your HubSpot account — reconnecting re-creates the missing properties. If a specific property was deliberately deleted in HubSpot, reconnecting restores it.

Error 400: property mismatch

A value SimpleEvents tried to write doesn't match the property's definition in HubSpot — most often because a SimpleEvents-managed property (like the QR code or event fields on the contact) was edited in HubSpot: its type was changed, or dropdown options were removed. Fix: restore the property to its original type in HubSpot (or reconnect, which repairs SimpleEvents-managed properties), then retry.

Error 500 when creating an

event

An unexpected failure on our side — these are automatically reported to our engineering team. Things worth trying while we look:

  • Retry once. If a second attempt also fails, don't keep retrying.
  • Check whether part of the event was created (form, list, or marketing event may exist in HubSpot) before recreating it, to avoid duplicates.
  • Contact support with the time of the error and your event's name — we can see the underlying error in our logs.

504 Gateway Timeout

The request took too long — usually during heavy operations (large batch imports, events with very large lists). The operation often continues in the background even though the page timed out. Wait a few minutes and refresh before retrying, and check whether the change actually landed.

"Missing scopes" / permission errors

Your HubSpot connection was authorized without a permission SimpleEvents now needs (common after new features are released, or if your HubSpot Super Admin restricted app permissions). Fix: reconnect HubSpot and accept all requested permissions. The full list of what we ask for and why: Scope needs.

Still stuck?

When you contact support, include: your Event ID (from the URL in your browser), the exact error text, and the time it happened. Those three things let us find the failure in our logs immediately.