Tips & FAQs
Known Issues
This page lists known limitations and in-progress fixes. It is updated with each Forge release.
Issue tracker
For the most current list of known issues and their status, refer to the Forge Roadmap (Admin > Roadmap in the sidebar). The Roadmap is updated in real time as issues are resolved and new ones are identified.
Current known issues
| Area | Issue | Workaround |
|---|---|---|
| Attendees | Bulk status update may time out for lists over 500 attendees if the Salesforce API limit is near. | Process in batches of 200. |
| Forms | Visibility rule evaluation is client-side only; server-side validation does not re-check conditions on submit. | Use Salesforce validation rules for critical business logic. |
| Sessions | Session conflict detection (two sessions at the same time in the same room) is advisory only — it does not block saving. | Review the Sessions tab for conflicts before finalizing the agenda. |
| Communications | Emails scheduled more than 90 days in advance may miss the send window if the event is cloned before the send date. | Recreate scheduled emails after cloning an event. |
| Finance tab | Revenue figures may lag by up to 60 seconds during high-volume checkout periods due to Salesforce query governor limits. | Refresh the Finance tab manually during peak registration periods. |
| Auctions (beta) | Live auction bid updates require a page refresh — real-time push is not yet implemented in Forge (it is available in the standalone Auctions app). | Refresh the Auctions tab during live events. |
| Recurring Events (beta) | Cloning a recurring event series copies only the parent record, not all child occurrences. | Manually create occurrences in the recurring event after cloning. |
| Dark mode | Some third-party embedded map widgets do not respect the dark mode theme. | Use the light theme when embedding maps in the Location tab. |
Reporting an issue
If you encounter a bug not listed here, use the Feedback button in Forge or contact Blackthorn support. Include: the URL where the issue occurred, steps to reproduce, what you expected to happen, and what actually happened. Attach a screenshot if possible.