Q: What causes SLA Not Starting on Incident in ServiceNow?

SLA start condition doesn't match incident's initial state — Navigate to Service Level Management > SLA Definitions, open your SLA, and check the 'Start condition' tab. Most incidents start in 'New' state, but your condition might require 'In Progress' or specific priority values that don't exist when the incident is first created. SLA definition is inactive or has wrong table — In your SLA definition record, verify the 'Active' checkbox is true and the 'Table' field is set to 'Incident [incident]' not 'Task [task]'. Check the 'Valid from' and 'Valid to' dates to ensure the SLA is currently in effect. SLA attachment workflow or business rule is not triggering — Check System Logs > All for any errors during incident creation. Look for the 'SLA workflow' in Workflow > Workflow Editor to see if it's active. Business rules that create task_sla records may be inactive or have condition issues. Service Level Management plugin is not activated — Navigate to System Definition > Plugins and search for 'Service Level Management' (com.snc.sla). If not active, you'll see an 'Activate' button. Also check if the SLA Engine (com.snc.sla.engine) plugin is active. Incident missing required field values for SLA condition — Your SLA start condition may reference fields like assignment_group, category, or business_service that are empty when the incident is created. Check the actual field values on a test incident against your SLA's start condition using condition builder preview.

Question 1

What causes SLA Not Starting on Incident in ServiceNow?

Accepted Answer

SLA start condition doesn't match incident's initial statehigh likelihood

Navigate to Service Level Management > SLA Definitions, open your SLA, and check the 'Start condition' tab. Most incidents start in 'New' state, but your condition might require 'In Progress' or specific priority values that don't exist when the incident is first created.

SLA definition is inactive or has wrong tablehigh likelihood

In your SLA definition record, verify the 'Active' checkbox is true and the 'Table' field is set to 'Incident [incident]' not 'Task [task]'. Check the 'Valid from' and 'Valid to' dates to ensure the SLA is currently in effect.

SLA attachment workflow or business rule is not triggeringmedium likelihood

Check System Logs > All for any errors during incident creation. Look for the 'SLA workflow' in Workflow > Workflow Editor to see if it's active. Business rules that create task_sla records may be inactive or have condition issues.

Service Level Management plugin is not activatedmedium likelihood

Navigate to System Definition > Plugins and search for 'Service Level Management' (com.snc.sla). If not active, you'll see an 'Activate' button. Also check if the SLA Engine (com.snc.sla.engine) plugin is active.

Incident missing required field values for SLA conditionmedium likelihood

Your SLA start condition may reference fields like assignment_group, category, or business_service that are empty when the incident is created. Check the actual field values on a test incident against your SLA's start condition using condition builder preview.

Question 2

How do you fix SLA Not Starting on Incident in ServiceNow?

Accepted Answer

How to fix it Navigate to Service Level Management > SLA Definitions and open your SLA definition. Verify the Table field shows Incident [incident] and Active is checked. Click the Start condition tab and examine your condition logic. Note which fields and values are required. Open a recent incident that should have triggered the SLA. Compare the incident's field values (state, priority, assignment_group, etc.) with your start condition requirements. If the condition includes State = In Progress but incidents start in New state, change the condition to include State = New or use State IN New,In Progress. Check Valid from and Valid to dates. Clear Valid to field if you want the SLA active indefinitely. Navigate to System Definition > Plugins and search for Service Level Management. Activate if not already active. Go to Workflow > Workflow Editor and search for SLA workflow. Ensure it's in Published state, not Draft. Check for business rules that might interfere. Go to System Definition > Business Rules and filter by Table = incident. Look for any that modify SLA-related fields or have SLA in the name. Create a test incident with field values that exactly match your SLA start condition. Save the incident and immediately check for task_sla records. Navigate to Service Level Management > Task SLAs and filter by Task = your test incident number. You should see a task_sla record with State = In progress.

Question 3

How do you prevent SLA Not Starting on Incident in ServiceNow?

Accepted Answer

Always test SLA definitions on a sub-production instance first with realistic incident data that matches your production patterns. Use condition builder's 'Test' button with actual incident record sys_ids to validate start conditions before activating SLAs. Set up SLA definition templates with common conditions (like 'State IN New,In Progress') to avoid state-related issues in future SLAs. Create business rules to populate required fields (assignment_group, category) during incident creation if your SLA conditions depend on them. Document SLA field dependencies and include them in incident creation training to ensure proper field population.

SLA Not Starting on Incident in ServiceNow

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge