@BobGassman - was it actually an email from messaging or an event reminder ?
Same thing, this was the resend of a message about an event
Pack 3224, Council Central Florida.
Originally sent Wednesday, April 1. Subject: Change to Pack Meeting Location.
Resent today at 10:48am.
Add Troop 571 and Troop 5749 and Pack 682 to the list of units having this happen.
Calendar reminder resend
Pack 0048, Pathway to Adventure Council, Ice Skating: Deep River Waterpark, originally sent 1/14/2026.
Let see if we can get some data. When did you get these emails?
- 1-3am CST
- 3-5am CST
- 5-7am
- 7-9am
- 9-noon
- afternoon
0
voters
I am in the same troop as jen wilkins. We got 2 both between 7-9 Cst
I guess the other question would be - if these are dupes. Can anyone tell if they sent the same time (of day) as the original?
I have a calendar event that was sent out today for an event that occurred in January 2026. I received it at 8:30AM EST.
The ID is: PD:20260120144900-53340.239-D88767AA2C4A4635BB6C833448811223
OK on this - if you got one of these from a calendar event - please go to the calendar event and post the URL - ex. https://advancements.scouting.org/calendar/event/6822834. - we need the number at the end
Greetings, Donovan.
It seems this thread may be covering two different issues:
- Duplicate event notifications being sent from the calendar in Scoutbook Plus.
- Duplicate emails being sent through the messaging feature in Scoutbook Plus.
Are we good addressing both issues in this thread, or would you prefer that I start a separate topic for the messaging issue?
I am new to Scoutbook this year and have only used the messaging feature, not the calendar, but the two issues seem potentially related.
I’m happy to promptly provide any information that would help troubleshoot this. We had our den meeting last night, and several parents were understandably confused by the old message being resent. We had to explain that it was a Scoutbook issue and that our plans had not changed.
At this point, I’m hesitant to continue using Scoutbook for den messages until the issue is resolved and will likely use my personal email instead.
Thank you for your consideration.
It does seem to be both - but the first clue I have been asked for is the event ID which I described above. The plain messages are harder to track down.
Donovan,
I did a little more digging in Gmail and found something that may be useful.
Original message - Aug. 27, 11:56 AM
Message-ID: E9A9879FFF874BD8B351017391348820@scouting.org
First duplicate - Aug. 28, 3:14 PM
Message-ID: AA3850CCE26E34D87A518CCDFDC52B33@scouting.org
Second duplicate - Sept. 24, 10:30 AM
Message-ID: AA3850CCE26E34D87A518CCDFDC52B33@scouting.org
Interestingly, the Sept. 24 message has the exact same Message-ID as the Aug. 28 duplicate, rather than a new Message-ID.
All three show as coming from noreply@scouting.org, with SPF/DKIM/DMARC passing and the same sending IP (43.228.184.211).
Since these were regular Scoutbook messages rather than event notifications, I don’t have an Event ID. If useful, I can also provide the downloaded originals/raw headers for all three messages.
@DonovanMcNeil I received an event reminder on Sept. 24 for an event that occurred on Aug. 29. Here is the event URL: Scoutbook Plus
Just following up to see if there have been any updates regarding this issue. I am still hesitant to use Scoutbook messaging until we know whether the duplicate-message issue has been resolved.
Thank you for your consideration.
We are told this is fixed - it just did not make the change log
Great. Thanks for looking into this.
