If a reChecker email hasn’t arrived, start with the specific event: which site, what happened, and when. Then check the address and channel settings, and look for the email in the mailbox itself. This will help you distinguish an incorrect expectation from a case that should be reported to support.
Not every new entry in a report necessarily generates an email. A daily summary also shouldn’t be taken as a promise of daily email delivery. Asking “Why didn’t I get an email about this event?” is more useful than asking “Why haven’t I received anything in a while?”.
Find the event you expected an email about
Open the Site monitoring dashboard and check the notifications for the relevant site. Note the event name and time. If you see an updated report but no notification, first confirm whether that case should generate a message.
For example, you see a new audit result but no separate event about a problem. This doesn’t mean an email was lost: a small change in the score doesn’t always warrant a notification. Don’t use the time you opened the dashboard as a substitute for the event time.
If the event is there, continue to the next step. Its entry in the dashboard confirms that the service recorded it. Whether the email reached the recipient is checked separately. The general process for reviewing results is described in the article about audits and monitoring.
Check the Email toggle and addresses
For the relevant site, open the “Settings” tab and the “Where to send notifications” section. Check the “Email” channel and the addresses shown. To change the addresses, click “Edit addresses”—the notification settings in your profile will open.
Check every character in each address. Make sure you’re looking at the right mailbox: your phone may have your personal email open, while notifications are configured for your work email. If no separate notification addresses are set, the account email is used.
After correcting the settings, wait for “Settings saved” and note the time of the change. This doesn’t prove that a future email will arrive, nor does it automatically resend an old one. If you enabled the channel after the event, include that sequence in your message to support.
External delivery also depends on the service’s current settings. If the address is correct and the channel is enabled, but the email for a specific event is missing, support needs to check that particular case.
Look for the email in your mailbox, not just your phone notifications
Open the mailbox in its own interface. Check your inbox, spam, archive, and any folders that rules move messages to. Search for emails from the relevant period using the name reChecker and the sender address, if you know it from a previous message.
If you find the email in another folder, note where. For a shared work address, check whether a colleague opened it or moved it to the archive. The absence of a pop-up notification on your phone doesn’t mean the email itself is missing.
Corporate email may have additional administrator rules. Give your administrator the expected recipient address, time, and email type. Ask them to check for the specific message; there’s no need to disable all security filters.
Send support the details you’ve already checked
Put together a short list:
- the site and event name;
- the event time, including the time zone;
- the recipient email and channel status;
- which folders and time period you checked;
- when you last actually received a similar email;
- whether you changed the address or settings before this incident.
Example message: “The event about a new problem on example.ru is visible in the dashboard 04.10 at 12:20 MSK. Email is enabled, and I verified the address support@example.ru. I checked the inbox, spam, and archive for 4 October, but the email isn’t there. The address hasn’t been changed. Please check delivery of this event.”
Your email password and access codes aren’t needed. If support says the email provider accepted the message, but you still can’t find it, pass that information to the mailbox administrator. Acceptance of a message for delivery doesn’t confirm that a person read it.
After fixing the issue, check both receipt and response
Wait for the next relevant event and ask the recipient to confirm the email, including the same site and time. Record the outcome: “06.10, email found in the inbox, responsible person opened the report.” This is more precise than “email is set up”.
If the mailbox is shared, assign someone to start reviewing the issue. An email won’t help the site if everyone is relying on a colleague. Use the notification recipients guide to hand off the task.
Until the channel is confirmed, agree to open the dashboard directly. After changing the email address or mail rules, repeat the check with a new event: a previously successful email was sent under the previous settings.