Check the package troubleshooting notes in Docs first—most installation snags (Registry r_… plugin IDs, missing EMDASH_ENCRYPTION_KEY on card checkout, or unconfigured email providers) have one-line fixes.
While your Eventual RSVP – Tickets licence is active, support is provided by email in English or French. Per §6 of the licence, we answer as soon as reasonably possible without a fixed SLA guarantee or custom site development obligation.
Eventual RSVP – Core, Eventual RSVP – Registrations, and eventual-capacity are MIT-licensed without warranty. Include the diagnostics below with your report.
Public routes intentionally conceal raw host errors behind TRY_AGAIN and log the root cause server-side. Including these four items avoids back-and-forth:
EmDash version, runtime host (Cloudflare Workers or Node), and plugin versions
For example: EmDash 1.4.0 on Cloudflare Workers Paid (with LOADER binding) or Node 24+, plus each installed plugin version.
Install mode (Registry r_… ID vs npm sandboxed/native) and email provider
State whether the plugin runs via sandboxed: [...], plugins: [...], or Registry (note your r_… ID), and which EmDash email provider sends your mail.
Steps to reproduce, exact route error code, browser network response, and Worker logs
Include the route path, HTTP status, error code, and the server-side log entry emitted when the request ran.
Never include real attendee data or live Stripe secrets
Strip visitor names/emails and never paste sk_live_…, whsec_…, or your EMDASH_ENCRYPTION_KEY.