Forum Discussion

alackey's avatar
alackey
Copper Contributor
Nov 02, 2026

News Posts: Distribution panel automatically pre-populating subject line from previous post

Hi everyone,

I'm encountering an issue when publishing News posts on our SharePoint site and wanted to see if anyone else has experienced this or knows of a fix.

Issue Description: When preparing to send/distribute a newly created News post, the distribution screen frequently pre-populates the email subject line field with the subject line/title from the previously published post instead of pulling from the current post's title.

Additional Context & Workaround:

  • Intermittent Behavior: This doesn't happen 100% of the time-sometimes the distribution panel loads with the correct title as expected.
  • Workaround: If I escape/close out of the distribution panel and use the standard pre-existing share screen instead, the subject line populates accurately every time.

Expected Behavior: The distribution subject line should consistently default to the current News post's title.

Actual Behavior: The subject line field often defaults to text from the prior post, requiring manual deletion and correction unless I close out and switch to the standard share panel.

Environment / Details:

  • Feature: SharePoint Online News Posts (Email Distribution / Send as Email)
  • Browser: Tested in Chrome 

Has anyone seen this caching/sticky field behavior in the new distribution panel before, or is there a known tenant setting or bug fix for this?

Any insights would be greatly appreciated! Thanks!

1 Reply

  • The new distribution panel is reusing a previous post’s subject, while the standard share panel correctly reads the current title. Microsoft’s SharePoint News for Email guidance says the post title should populate the subject automatically and that you can edit that field before sending.

     

    For now, review the subject before every distribution, or continue using the working share route. To isolate the problem, test the same two posts in a fresh private browser window and in Edge, then ask another author to repeat the sequence. Note whether it also affects a completely new post rather than a copied page.

     

    If it reproduces across browsers and authors, have your administrator check Service health and raise a SharePoint support case with both page addresses, timestamps, and the exact reproduction sequence. I cannot confirm a published fix or tenant setting for this symptom; the comparison tests avoid assuming that Chrome’s cache is responsible.