Email handling as apps grow – how are you structuring it?

Certified Senior Developer

In one of our production apps, we currently send emails directly from the main process models using the Send Email smart service.

As volume is increasing, we’re starting to rethink whether this is the best long-term approach.

For those who’ve worked on larger implementations — do you keep email logic in the main process, or move it to a reusable subprocess? Also curious how you’re handling retries and basic monitoring in production.

Just trying to sense-check our design as the app scales.

  Discussion posts and replies are publicly visible

Parents
  • Certified Senior Developer

    Thanks everyone, this is helpful.

    We’re moving toward a centralized async email utility subprocess so the core models stay focused on business flow.

    We’ll standardize sender/template config there and contain retries + failure logging within that layer.

    Appreciate the insights.

Reply
  • Certified Senior Developer

    Thanks everyone, this is helpful.

    We’re moving toward a centralized async email utility subprocess so the core models stay focused on business flow.

    We’ll standardize sender/template config there and contain retries + failure logging within that layer.

    Appreciate the insights.

Children
No Data