Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Why SLAs are not posting e-mail notifications in the incident activity stream - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Why SLAs are not posting e-mail notifications in the incident activity stream
KB0779115

Why SLAs are not posting e-mail notifications in the incident activity stream


673 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

The user's P1 incidents are not posting e-mail updates to the activity stream on the related task record (e.g. Incident), even after one hour. 

Resolution

To begin with, it is worth noting that this functionality does not exist naturally in an Out of Box (OOB) instance. Within an OOB instance, there is no native posting of this information to the parent task which the task_sla is on. Rather, such activity stream updates are posted directly to the task_sla, as that is where the workflow is running. The task_sla form layout needs to be configured to show this, though. This is expected.

It was found that the user accomplished these updates via a custom workflow with a custom workflow activity within it and reported that they could see this process working fine in their Production instance, but not in their Development instance.

The reason that this is working in Production and not in Development is that the user is using the custom workflow on some SLA Definitions in their Production instance, but in Development, they are using the OOB "Default SLA Workflow", where this functionality does not exist.

When the user modified the workflow associated with their SLA Definitions in their Development instance to utilize their custom workflow, the behavior was corrected and their custom functionality worked once again.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.