Skip to content
MassTransit Documentation

Customer Support

As a MassTransit subscriber, you have a direct line to the maintainers. Whether you’re debugging a production issue, designing a complex workflow, or need architectural guidance, our team is here to help.

If your organization has an active MassTransit subscription, you can access support directly. To get help using MassTransit, contact us at: support@massient.com

If you are not an active subscriber, sign up now to unlock support access.

Before you open a ticket

Section titled “Before you open a ticket”

Support is included with your subscription, so open a ticket whenever you need help. A few quick checks up front usually lead to faster, more accurate answers.

  • Confirm the issue still occurs on the latest MassTransit patch version you can reasonably test
  • Include exact package versions, and note whether you reproduced on a newer version
  • Isolate the smallest reproducible example, even if it is only a reduced configuration
  • Redact secrets from logs and configuration (connection strings, keys, tokens, credentials)
  • Remove personal or sensitive data from payloads, headers, and screenshots

What makes a good support ticket

Section titled “What makes a good support ticket”

High quality tickets are actionable. They include enough context to quickly identify whether the issue is configuration, environment, transport, or code related.

  • A clear subject line that describes the issue and impact
  • What you expected to happen
  • What actually happened
  • Exact versions: MassTransit, .NET, transport, and related packages
  • Environment details: OS, hosting model, cloud/on-prem, and deployment setup
  • Full exception details and stack traces
  • Relevant logs with timestamps around the failure
  • Bus/endpoint configuration snippets (with sensitive values removed)
  • Steps to reproduce, including sample messages or payloads
  • Any recent changes (upgrades, deploys, config changes)

Support communication style

Section titled “Support communication style”

To keep support fast and accurate, we prefer:

  • Prefer copy/pasted logs, stack traces, and configuration over screenshots
  • Prefer full error context over a single exception line
  • Prefer exact versions and environment details over “latest” or “standard setup”
  • Prefer a small reproducible example over a broad project description
  • Prefer expected vs actual behavior over “it doesn’t work”
  • Prefer recent change history over “nothing changed”

Community Resources

Section titled “Community Resources”

In addition to customer support, you can also engage with the community: