---
schema_version: "1"
id: c1337cd2b0ebf2947fd1e993af1e2570b342890db1e5d0582e2a6d3da3395e68
title: Milestone Actions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/sla_milestones_actions_overview.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.sla_milestones_actions_overview.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ba20473777369896dae82560d4314ba67da892d3c88ae609eaf4a8487559badf
description: Milestone actions are time-dependent workflow actions that occur on milestones in an SLA policy. Actions can be added to milestones after the milestone is added to an SLA policy.
products:
  - Service Cloud
release: "264"
---
# Milestone Actions

Milestone actions are time-dependent workflow actions that occur on milestones in an SLA policy. Actions can be added to milestones after the milestone is added to an SLA policy.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.service_editions_reference.htm&amp;language=en_US" target="_blank">View supported editions</a>.</td></tr></tbody></table>

For example, you can create a milestone action that:

- Sends an email alert to certain users an hour before a First Response milestone is near violation
- Updates certain fields on a case one minute after a First Response milestone successfully completes

You can add three types of actions to milestones:

 
| Action Type | Description |
| --- | --- |
| ![Success action icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/support/images/confirm16.png) Success Actions | The actions to take when a milestone successfully completes. Success actions still fire on milestones that are completed late. |
| ![warning](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/support/images/entitlements/warning16.png) Warning Actions | The actions to take when a milestone is near violation. |
| ![violation action icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/support/images/error16.png) Violation Actions | The actions to take when a milestone is violated. |

You can automate these actions for each action type:

  
| Workflow Action | What It Does | Example |
| --- | --- | --- |
| Task | Create a workflow task | Create a task for a support rep to call a customer when a First Response milestone is violated. |
| Email Alert | Create an email alert | Notify case owners when a First Response milestone on their case is near violation. |
| Field Update | Define a field update | Update the case Priority field to `High` when a First Response milestone is near violation. |
| Flow | Create an autolaunched flow | Send a Slack notification to support reps when a First Response milestone is near violation. The new flow created via the workflow action is only visible as long as it is associated with the milestone. Once the association is removed the flow is not available for selection again. |
| Outbound Message | Define an outbound message | Send data about parts or services to an external system after a First Response milestone is completed. |
| Select Existing Action | Select an existing action | Use an existing email alert to notify a case owner when their case is near violation of a first response. |

Things to consider while using milestone actions:

- Time trigger action calculations don’t account for a case’s milestone business hours.
- Field updates temporarily lock a case and can trigger automation such as case assignment rules. Field updates have a processing time limit of 10 seconds. Longer updates fail without an error. Reasons for this type of failure include updates to a field that’s already locked or complex business logic that runs longer than 10 seconds.
- Warning and Violation actions don’t honor the business hours for the minutes, hours, and days, before or after the milestone target date. These actions are converted into minutes on a 24-hour clock, and don’t use business hours.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support-264-0-0-production-enus/dd14551c-a772-4db6-9a1d-d84df8df2980/images/icon_example.png)

Example

Acme has their business hours set to 8 hours a day for 5 days a week (Monday though Friday). In minutes, that’s 480 minutes per day. They have a milestone with a time trigger of 1,919 minutes, which is four full business days. 5,760 minutes is four 24-hour days. They defined a warning action time trigger as "2 Days Before". Here, that means 2,880 minutes before the milestone target date.

A case comes in that meets the milestone entry criteria on Monday at 9 AM. The target date for the case is 16:59 PM on the coming Thursday. Because the warning action uses a 24-hour clock, the warning must be issued 2,880 minutes, or six business days, beforehand. Given this setup requires the warning to be issued in the past, or on the previous Thursday, the warning action executes immediately.