Common Gotchas

These are the most common mistakes and surprises that new Forge users encounter. Read through them before your first event launch.

Changing event capacity after launch

If you lower the Maximum_Attendees__c field after the event is live, existing registrations are not affected — but new registrations will be blocked if the count exceeds the new limit. If you raise capacity, waitlisted attendees are not automatically moved to Registered; you need to manually promote them or re-open registration.

Cancelling an attendee does not issue a refund

Changing an attendee's status to Cancelled in Forge only updates the conference360__Attendee__c record status. It does not trigger a refund. To refund a payment, go to the attendee's record, expand the Transactions section, and click Refund on the relevant transaction. Do this before or after changing the status.

Deleting a ticket type with existing registrations

Forge will warn you if you try to delete (or set to Off Sale) a ticket that has existing Attendee records. If you must remove a ticket, first reassign affected attendees to another ticket type, then remove the original.

Form answers not appearing in Salesforce

If registrants are completing the form but answers are not appearing on Contact or Attendee records in Salesforce, check: (1) the field mapping on the Form_Element__c records, (2) Salesforce field-level security (if the Forge integration user lacks Write FLS on the target field, the write is silently skipped), (3) any validation rules on the target object.

Duplicate Contact records

Forge matches registrants to existing Salesforce Contact records by email address. If your org has duplicate Contacts with the same email, a new registration may link to the wrong Contact — or create a Lead instead. Clean up duplicate Contacts in Salesforce before running high-volume events.

Session enrollment vs. event registration

Registering for an event and enrolling in a session are separate actions. An attendee can be Registered for the event but have zero session enrollments. The Session Enrollment Form only appears if you have attached one to the session and the registrant selected a ticket type linked to that session.

Cloning copies configuration, not attendees

The Clone event feature copies ticket types, form configuration, page settings, and communications templates. It does not copy attendees, transactions, or speaker/sponsor confirmations. Each cloned event starts with zero registrations.

Salesforce session expiry in Forge

If your Salesforce session expires while you are working in Forge, you may see a spinner that never resolves or an error toast. Refresh the page — Forge will detect the expired session and redirect you to log in again. You will not lose any data you have already saved.

Beta features are opt-in, not opt-out

Beta features are disabled by default. If you don't see a tab or feature mentioned in this documentation, check whether it requires beta opt-in at /beta.