> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/general-information/devops-email-notifications.md).

# DevOps Email Notifications

## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) Overview

DevOps sends email notifications to inform users about events related to their DevOps activity. There are two types of notifications: Scheduled and Activity. Scheduled notifications are sent on a regular schedule and include DevOps items relevant to the user. Activity notifications are sent when a user-initiated action completes, either successfully or unsuccessfully. All notification emails sent by DevOps are explained below.

{% hint style="info" %}

#### Notification Settings

Currently, there are no settings to change how email notifications operate in DevOps.
{% endhint %}

## Scheduled Notifications

### Weekly Summary \[Sunday at 3 PM UTC Weekly]

This email is sent on a weekly schedule, every Sunday at 3 PM UTC. It goes out when either of the situations described below applies. Each user receives only one email per week, and it includes all relevant items. If no items apply to a user, that user does not receive this email.

* **Uncommitted Components**: If components have been retrieved from an organization but not yet committed to a branch, the notification is sent to the user who connected that organization in Global Settings.
* **Branches Awaiting Action**: If a branch has had no activity for 48 or more hours since its last commit, the notification is sent to the user who made that commit.

### Unregistered Users \[Monday at 3 PM UTC Weekly]

This weekly email notifies people who modified components in a connected Sandbox Salesforce org but do not have an account in your Flosum Cloud Apps tenant. It is sent only when all three of the following conditions are met:

* The user's email appears in the **LastModifiedBy** field of a component retrieved from a Sandbox organization connected to DevOps.
* That email is not currently registered in the tenant (including both **Confirmed** and **ForceResetPassword** user accounts).
* The user modified the component within the last 30 days.

The email is sent to the address that Salesforce provides for the unregistered user.

## Activity Notifications

The table below lists the activities that trigger an email notification to the user who started the activity. The email subject will state the Activity and its Status (e.g., Completed or Failed).

<table><thead><tr><th width="180">Activity</th><th>Description</th></tr></thead><tbody><tr><td>Pipeline</td><td>An email notification is sent when a pipeline is completed or fails.</td></tr><tr><td>Validation</td><td>An email notification is sent when a branch Validation job is completed or fails.</td></tr><tr><td>Metadata Retrieval</td><td>An email notification is sent when a user-initiated metadata retrieval is completed or fails.</td></tr><tr><td>Deployment</td><td>An email notification is sent when a branch Deployment job is completed or fails.</td></tr><tr><td>Smart Merge</td><td>An email notification is sent when a Smart Merge job is completed or fails.</td></tr><tr><td>Pull Request</td><td>An email notification is sent when a Pull Request is created or merged.</td></tr><tr><td>Rollback</td><td>An email notification is sent when a deployment Rollback is completed or fails.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flosum.com/devops/general-information/devops-email-notifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.