#Trailhead Challenges1.921 utenti parlano di questo argomento

A ruleset that errors on run is almost always one of these: 

1. No source data mapped yet. Identity Resolution runs on the Individual DMO - if no data stream is mapped to Individual (and ingested), there are no records to resolve and the run fails. In Data Cloud > Data Streams, confirm your stream ran and is mapped to the Individual DMO with the match field populated. 

2. Incomplete ruleset. It needs at least one match rule (with criteria) plus reconciliation rules - an empty or match-rule-less ruleset errors. 

3. The match field your rule uses must actually exist and be populated on Individual. 

In a Trailhead module the order matters: ingest the data and map it to Individual first, then create and run the ruleset. Doing identity resolution before the data is mapped is the usual cause. 

If none of that is it, paste the exact error text and I will pinpoint it. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks 🙂

That error is the grader checking your StringArrayTest class, and 'does not return the proper number of strings' means the count is off. Check these: 

1. The method is public static and returns a List of String: public static List<String> generateStringList(Integer n) 

2. It returns exactly n items - the usual slip is the loop bounds. Use for (Integer i = 0; i < n; i++) - start at 0, strictly less-than n. Using i <= n gives n+1 items; starting at 1 gives n-1 - either one trips 'proper number of strings.' 

3. Each item is 'Test ' + i (with the space, index starting at 0), so the list is 'Test 0', 'Test 1', up to 'Test ' + (n-1). 

4. The class is named exactly StringArrayTest. 

Minimal version: 

public class StringArrayTest { 

  public static List<String> generateStringList(Integer n) { 

    List<String> myList = new List<String>(); 

    for (Integer i = 0; i < n; i++) { myList.add('Test ' + i); } 

    return myList; 

  } 

} 

Save, then re-run Check Challenge. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks 🙂

Short answer: no - native Case Escalation Rules only let you pick 0 or 30 minutes for 'Age Over' (you enter the hours, then choose 0 or 30 from the dropdown). Custom values like 12 or 20 minutes are not possible there; it is a fixed platform limit. 

For minute-precise escalation, use one of these instead: 

1. Record-Triggered Flow with a Scheduled Path (easiest): add a scheduled path set to run, say, 12 or 20 minutes after your date/time field (or after the case is created / meets criteria), and put the escalation action - reassign to a queue, send an email, update a field - in that path. Scheduled paths accept any custom minute value. 

2. Entitlements + Milestones (the full SLA framework): 'Minutes to Complete Milestone' accepts any number, and Milestone Actions fire at exactly that time - ideal if you are tracking support SLAs. 

Go with the Flow scheduled path if you just need custom timing; use Milestones if you want a proper SLA model on Cases. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks 🙂