Emails that go to the right people

One company user received 20 message request emails over a weekend. Their notification settings showed no positions selected at all.

Those emails went to everyone at a company and were then trimmed down by each person's position preferences. If someone had no preferences stored, there was nothing to trim, so they got everything. This release sorts out who is on the list, and stops the emails that were being dropped on the way out.

Fixes

• Message requests: No stored preferences now means you're not a recipient, rather than a recipient for every position at your company. Around 45,000 preference rows were filled in from the positions people already hold, and newly invited users start muted, then pick up positions when they join a hiring team.

• Chaser emails: Reminders about one unanswered application on one position went to the whole company, so the 40 accounts with nothing stored were getting a chaser for every position going. They now go to the hiring team, plus anyone already in the conversation.

• Replies in a thread you're part of: If you were talking to someone about a position you don't own, your position preferences quietly stopped their replies reaching you. 6 of 221 conversation pairs over 14 days were in that state, 4 of them not on the hiring team. Being in the thread is now enough. Switching new message emails off still switches them off.

• Emails that never arrived: Two templates hit an error while rendering, and a failed render meant the email was never sent and never retried. 29 went missing in 15 days, roughly 2 a day, all of them digests and mention notifications. A comment mention on someone outside a shortlist accounted for 8, and now sends with a link to that person in search.

• A blip in the cache: When cord briefly couldn't read its cached email rules, it read that as "this person has no rules" and dropped every email in flight. It now goes back to the database instead.

• Position preferences on a new role: Creating or updating a position didn't wait for the hiring team's email preferences to save, so a member could end up holding a position with nothing stored against it. That write now finishes before the position is confirmed.

• Unsubscribe in demo emails: Clicking Unsubscribe always landed on "Unsubscribe failed". It works now. Those emails were also printing the redaction placeholder as it was written, so a profile read "Senior Cloud Engineer at Redacted" and "M. Ipsum". They now read "Senior Cloud Engineer" and "M.", with a line explaining that full profiles come with a subscription.

• Dates in emails: Work and education ranges rendered as "-05 '25 - Present". They now read "May '25 - Present".