1. Log in to the Manager Portal and select the appropriate Organization from the upper right-hand corner.

2. Select Settings from the top menu bar.

3. Select Everbridge Open from the drop-down menu.

4. Click the number for Emails Received next to the desired integration.

5. Identify if the email was received per the Ingestion Time.

6. If a sent email does not appear in this list, skip to the Unfiltered Emails section below.

If the email ingestion integration did not receive the email but it can be validated that the email was sent, find the Unfiltered Emails inbox with the steps below:

1. Log in to the Manager Portal and select the appropriate Organization from the upper right-hand corner.

2. Select Settings from the top menu bar.

3. Select Everbridge Open from the drop-down menu.

4. Click on the Unfiltered Emails link on the upper right.

5. If the email sent is in this list, it means that it did not match the requirements in any ingestion configuration.

6. Update the emails sent to match the ingestion configuration.

7. If a sent email does not appear in this list, skip to the Validate the Sender and Recipient section below.

If the email was not received by either the email ingestion integration or the unfiltered emails inbox, verify that the email sender and the integration recipient are correct:

1. Log in to the Manager Portal and select the appropriate Organization from the upper right-hand corner.

2. Select Settings from the top menu bar.

3. Select Everbridge Open from the drop-down menu.

4. Click the pencil icon next to the desired integration.

5. Review and verify the values in Sent from: and And received at: text fields.

6. If the integration is configured to accept messages only from a specific address or domain, remember that emails sent from other providers (for example, Yahoo or Gmail) will not be accepted.

If emails are consistently ending up in the unfiltered queue or incidents stop triggering as expected, try the following:

1. Update the 'Sent From' email address in the integration settings to allow emails from any '@<company-domain>' address, if applicable.

2. If there are issues with parsing date and time information from the email body, consider using a regular expression to capture this information as text instead of trying to parse it directly.

3. Check the 'send update notification' setting in your Everbridge Open settings. If this is set to 'never', updates to existing Source IDs will be ignored. Ensure this setting is configured correctly to allow updates to be processed.

4. For high volumes of incoming emails from monitoring systems (like SCOM or SolarWinds), note that Everbridge can process large numbers of emails without specific limitations. While all emails will be received and processed, processing speed may vary during peak volumes and large bursts (for example, thousands of emails within minutes) can create a temporary backlog and delay some notifications until the queue is cleared. No special configuration is needed for high-volume email ingestion.

5. If notifications do not trigger and it appears that emails are not reaching Everbridge at all, verify that the sending system is addressing the correct integration email, check the sender logs to confirm messages were handed off, and review any mail gateway or filtering appliances that might be blocking or altering the messages.

6. Use the Unfiltered Emails log to review failed messages. Confirm that the From (actual) address and the Received At (integration) address in the log entry match the ingestion configuration, that the integration still references an existing incident or template, and that any RegEx or variable settings used to parse the body still match the current message format.

If you're unable to create or modify Email Ingestion settings in Everbridge, it may be due to permission or user-status issues:

1. When you have multiple roles in Everbridge, your default role must have email ingestion edit privileges.

2. If your default role lacks these permissions, you may encounter errors when trying to create or modify Email Ingestion settings.

3. To resolve this issue, switch your default role to an Organization Admin role or a role specifically enabled for email ingestion permissions.

4. Be aware that Email Ingestions can also stop working if the last user who edited the integration has been disabled, deleted, or no longer has an Organization Admin default role.