AlanM reports that new users created via API on a Discourse site only begin receiving Activity Summaries after their first site visit, despite being set as active and approved. He hoped summaries would arrive before the first visit to encourage engagement. Moin suggests the issue may stem from the suppress digest email after days setting or from users never visiting, referencing a known behavior for SSO-created users. AlanM acknowledges the suggestion and plans to implement the recommended changes. pfaffman adds that creating truly active users can be tricky — even if marked as active, they may still be pending email validation, which could block summaries. This mirrors a recent issue he encountered when creating users via Rails. The thread highlights that user activation status alone may not be sufficient to trigger Activity Summaries; actual site visitation or email validation may be required. The discussion centers on configuration nuances around digest delivery for API-created users, with suggestions pointing to validation state and visit history as potential blockers. Moin cites a meta thread for deeper context on SSO and digest behavior, while pfaffman emphasizes the complexity of user state in Discourse’s backend. Overall, the issue appears to be a combination of user status, visit history, and possibly email validation, rather than a missing setting.
Have recently set up a new Discourse site with all users being created via API calls with active and approved status set to true, also digest and suppress intervals were set in the site settings.
I am finding that users only start receiving Activity Summaries after their first visit to the site. I was hoping that all users would receive Activity Summaries prior to visiting the site as a means of encouraging them to make their first visit.
Have I missed a setting to make this happen, or is there something else I need to do? Thanks.
It’s harder to create an active user than you might think. I suspect those users are waiting for the email to be validated even though they are marked as active. I had a similar problem recently when I created a user with rails.