Additional Recipients for Workflow Notifications
acknowledged
Mattia
Currently, Seqera Platform's notification system informs only the user who initiated a workflow about its finalization status. Enabling users to customize their notification preferences for workflows in a workspace would help ensure notifications are relevant and tailored to individual preferences and improve collaboration.
We should also enable adding recipients both in the to: line as well as cc:.
F
Flamingo pink Python
Hi, is there an ETA on the completion of this? At a minimum, we really need to be able to include a "cc" email list with job submission from
tw
. It would be super helpful to know if / when we could expect this feature because otherwise we would end up being forced to create our own internal bespoke solution to this. Would much prefer that Seqera Platform can just do it. Thanks!Drew DiPalma
Flamingo pink Python Hi – We don't have a set ETA for this at the moment, but we will look into whether there's a quick extension we can make here.
F
Flamingo pink Python
thanks Rob Newman Drew DiPalma
I would also like to give a '+1' to the merged in post about 'Enable "Send notification email on workflow completion" for all Tower users by default', since its merged I can't upvote it separately it seems. This would be a huge help.
Rob Newman
Flamingo pink Python: When your post is merged with an existing post, your vote and comments are all included.
Rob Newman
Merged in a post:
The Seqera Platform pipeline notification emails should include cc, attachments
F
Flamingo pink Python
The email sent by Seqera Platform upon the completion of the pipeline needs these features;
- ability to configure your pipeline run to include other email's in the recipient To field or 'cc' field when sending the pipeline notification
Note that for the inclusion of the 'cc' or extra recipient emails, this function should also be exposed when submitting the pipeline run via API and via 'tw' cli as well.
Rob Newman
Flamingo pink Python: We have split the "attach files to the email" to this separate feature request: https://feedback.seqera.io/feature-requests/p/attach-pipeline-output-files-to-email-notifications
Drew DiPalma
Merged in a post:
Allow ability to specify email addresses to receive workspace notifications
Y
Yellow sunshine Firefly
Currently a user has to subscribe to receive notifications for a workspace. In a production, automated environment, this is inefficient and results in the desired users not getting notifications. A workspace for production pipelines should have the ability to specify a email address (like a distribution list) that is not tied to a user to ensure a entire team, including non-tower users, can get notifications that a run failed/succeeded.
We currently have to have a service account in Tower that receives all Tower emails, make an outlook rule on that inbox, and send emails to a DL.
Drew DiPalma
Merged in a post:
Enable "Send notification email on workflow completion" for all Tower users by default
A
Azure Dingo
Seqera Platform users can select an option in their profile which will cause an email to be sent to them each time a Run is completed. Could this option be automatically configured at the organization level?
Existing configuration does not allow the email option to automatically default to
Yes
for all users in an organization.Drew DiPalma
Merged in a post:
Automatic Email Pings Upon Pipeline Failure (Configurable on Pipeline)
Q
Quicksand Mink
I would like to set up an action with a pipeline and get an email if the pipeline fails. I know you can make it happen inside the code or as part of Nextflow options. My question is what is the easier way, and how I need to configure the Seqera Platform server to send the email. The platform has already information about the SMTP service from AWS, that is being used to log in. I can see how this is possible, I was wondering if somebody have that information in a way that is easy to share so we don't invest time figuring out.
Rob Newman
acknowledged
F
Flamingo pink Python
Is it possible also to make this feature available via the cli Tower launcher and/or API requests?