Chili Piper · Distro · Salesforce

Chili Piper Distro Logs: How to Read, Filter and Fix Lead Routing

Every record Chili Piper Distro touches leaves a trail in the Distro Log: whether it was routed, who got it, and which rule decided. This guide shows where to find the log, what each status means, how to read a record's evaluation, and how to fix the errors that stop leads reaching a rep.

Key Takeaways

  • The Distro Log is Chili Piper's audit trail for routing. It shows every Salesforce record a router evaluated, its status, who it was assigned to and why.
  • Open it from Distro → Logs. Admins and Workspace Managers on the All Products or Routing & Scheduling plans can see it.
  • Seven statuses matter: Routed, Error, No Match, No Match to Entry Rule, Delayed, Not Triggered and Discarded by Delay. The last two are hidden until you select them.
  • Open any record to see its Record Evaluation (field, operator, value and the data Distro actually saw). An empty Data cell explains most No Match results.
  • Most errors trace back to Salesforce: push topic or Streaming API limits, validation and duplicate rules, missing permissions or an expired connection.

Chili Piper Distro Logs answer the question every sales operations team asks sooner or later: "Where did that lead go?" When a hot inbound lead sits unassigned, or the same rep keeps getting every enterprise account, the log shows exactly what Distro saw, which rule it applied and what it did next. You no longer have to guess from Salesforce field history.

This guide is for revenue operations and Salesforce admins at growing and mid-market companies that route leads, contacts, accounts or opportunities with Chili Piper Distro. It replaces our 2023 post, corrects what that post got wrong, and adds the statuses, error fixes and log details Chili Piper has introduced since.

Section 01 · Definition

What Are Chili Piper Distro Logs?

Distro Logs are a record-by-record audit trail of Chili Piper's routing engine. For each CRM router, the log lists the Salesforce records that triggered it, whether each one was routed, who it was assigned to, and which conditions matched. Teams use it to confirm routing works, explain assignments and troubleshoot records that never reached a rep.

Distro is Chili Piper's routing product for Salesforce. A router listens for a Salesforce event (a record created, or updated on chosen fields) and then runs the record through entry rules, routing rules and paths. It assigns an owner by round robin or by existing CRM ownership, and can update fields, create tasks or opportunities, convert leads and enforce SLAs. By default it routes Leads, Contacts, Accounts, Opportunities and Cases, and other standard or custom objects can be switched on, according to Chili Piper's Distro glossary for admins.

What the log is: a read-and-troubleshoot view of routing decisions, with a manual re-route for errored records and a retry for failed CRM actions.

What it is not: a tool for sending logs to email, SMS or Slack. Slack and email in Distro notify the assigned rep or chase an SLA. They don't distribute logs.

Section 02 · Access

How Do You Open the Distro Log in Chili Piper?

In Chili Piper, open the Distro section and click Logs in the left-hand navigation. You first see a list of your CRM routers. Select a router to open its records. The log is available to Admins and Workspace Managers on the All Products or Routing & Scheduling plans, as stated in Chili Piper's Distro Logs guide.

  1. 1

    Go to Distro → Logs. The router list shows each router's status (active or inactive), trigger object, trigger type, and records routed and not routed in the last 24 hours.

  2. 2

    Pick the router to investigate. A high "not routed" count next to an active router is the quickest signal that something needs attention.

  3. 3

    Open its records. You land on a filterable list of every record that router evaluated, with summary counts above it.

  4. 4

    Jump between router and log. Since 2024, routers link to their logs and logs link back with View Router, so you can fix a rule and check the result without hunting through menus.

Chili Piper Distro Log router list showing five CRM routers with router status, routed and not routed counts for the last 24 hours
The Distro Log router list: each router with its status and its routed and not-routed counts for the last 24 hours. Screens in this guide were captured in 2023, so labels in the current app may differ slightly.
Section 03 · Filters

How Do You Filter Distro Log Records?

Four filters and a search bar narrow the list: time period, Assigned To, Status and Distribution Method. Above the list, summary counts show how many records the router saw, how many it routed successfully and how many it did not route. The not-routed count is split into Delayed, Errors and No Match, so you can see the type of problem first.

FilterWhat it doesUse it to
Time period (under Distribution)Defaults to Today; switch to other ranges such as the last 7 days or a custom rangeLine the log up with the moment a rep or marketer reported a problem
Assigned ToShows only records assigned to the reps you pickCheck whether one rep is getting too much, or nothing at all
StatusShows chosen statuses; Not Triggered and Discarded by Delay are hidden by defaultIsolate Errors or No Match records for troubleshooting
Distribution MethodSplits records by round robin, ownership, or no distributionSeparate fairness questions (round robin) from account-ownership questions
SearchFinds a single recordAnswer "where did this lead go?" in seconds
Distro Log time filter dropdown open, listing Custom, Last 24 Hours, Last 7 days, This Week and Last Week
The time filter. Pick the range that covers the reported problem before reading the counts.
Distro Log Assigned To filter open with a Select All option and a checkbox for each rep
The Assigned To filter shows records per rep, which is useful when someone says they are "getting nothing".
Distro Log Status filter open with Delayed, Errored, No Match and Routed selected and Not Triggered unselected
The Status filter. Not Triggered is left unticked by default; tick it when a record seems never to have reached the router.
Section 04 · Statuses

What Does Each Distro Log Status Mean?

A record's status tells you how far it got: Routed means a rep owns it; Error means something failed; the two No Match statuses mean a rule stopped it; Delayed means it is still waiting. Not Triggered and Discarded by Delay are hidden by default because they are usually expected. Each status points to a different fix.

StatusWhat it meansWhat to check
RoutedThe record was assigned to a team memberNothing, unless the assignee looks wrong. Then read the Record Evaluation
ErrorAn error occurred while routing or running an actionThe error message at the top of the record, then re-route or retry once fixed
No MatchThe record failed record evaluation or matched no routeEmpty or unexpected field values, and whether a Catch-all path exists
No Match to Entry RuleThe router's entry rule blocked the recordWhether the entry rule is stricter than intended
DelayedThe router has a delay and the record is not routed yet; the status updates when the delay endsOnly a problem if the delay is longer than your speed-to-lead target
Not TriggeredThe record did not meet the trigger criteria (hidden by default)The trigger's object, event and field conditions
Discarded by DelayThe record was updated while already waiting to be routed, so it was not routed again (hidden by default)Usually expected, for example when an enrichment tool updates a new lead during the delay

Older guides, including our original post, call routed records "Assigned". Chili Piper's current documentation uses Routed, and adds the No Match to Entry Rule and Discarded by Delay statuses.

Section 05 · Record Detail

How Do You See Why a Record Was or Wasn't Routed?

Open the record from the log and expand its Record Evaluation. Distro shows the date and time, the trigger it matched, the rules it evaluated and, for each condition, the field, operator, expected value and the data it actually found. Where the Data cell is empty, the record had no value for that field, which is the most common cause of a No Match.

Distro Log record evaluation showing a rule's conditions joined by AND and OR, each with field, operator, value and data, and a check mark on each matched condition
A rule's evaluation: each condition shows the field, operator, value and the data Distro saw, with a tick where it matched. Here the Country condition passed on its "is null" branch, not the Canada and United States list.

A typical example: a web form leaves Country blank, the US routing rule expects "United States", and the lead falls to No Match. The evaluation shows the empty Data cell straight away. The fix is either a required form field, an enrichment step before routing, or a Catch-all path that sends incomplete records to a triage queue.

What else the record view shows today

  • Match results. CRM matching nodes record outcomes such as "Lead to Account Match = True", with a link to the matched record.
  • Assignment tables, enrichment and spam checks. According to Chili Piper's 2026 product updates, the log shows which assignment table row matched, and the before and after values of each enrichment. Records stopped by the Spam Checker carry a "Blocked as Spam" banner with the score and the checks that failed.
  • Actions you can take. Errored routing can be retried with Re-Route this record. Failed CRM actions show at the top of the entry with a Try Again button, and View Router opens the router that made the decision.
Section 06 · Troubleshooting

What Are the Most Common Distro Log Errors, and How Do You Fix Them?

Chili Piper names three errors as the most common: "Not enough push topics", "Streaming API Event Limit" and "Unable to update action". The first two are Salesforce platform limits. The third means a route has no valid action, or Salesforce refused the update. Salesforce API errors such as validation rules and duplicate rules make up most of the rest.

Error in the logWhat it meansFix
Not enough push topicsDistro listens to Salesforce through push topics, and your Salesforce edition's allocation is used upDelete unused push topics (Distro's are named ChiliPiper- plus the object) or free some up in Workbench; otherwise raise the allocation
Streaming API Event LimitThe org reached its Streaming API event limit, and Distro stops until it resetsFind other integrations consuming events, and reduce triggers on noisy fields
Unable to update actionThe route has no action or an invalid one, or Salesforce couldn't update the recordCheck the route's assignment node, then the Salesforce error shown with it
Duplicates Detected / Custom Validation RuleA Salesforce duplicate or validation rule rejected Distro's updateExclude the Chili Piper integration user from those rules, as Chili Piper recommends
Required Field Missing / Invalid or Restricted PicklistA field update writes an empty or unsupported valueCorrect the field update node, or add the value to the picklist
INSUFFICIENT_ACCESSThe connected user can't see the recordGrant View All Data or View All Records to the Chili Piper user
Token Expired / Invalid CredentialsThe Salesforce connection brokeReconnect Salesforce in Chili Piper's integrations settings

Chili Piper keeps the full list, with fixes, in Common Salesforce API Error Alerts. After a fix, return to the log and use Re-Route this record or Try Again on the affected records. Don't wait for the next trigger, because an unchanged record may never fire it.

Section 07 · Hidden Causes

Why Is a Record Not Routed When There Is No Error?

Usually because a setting worked as designed: a rep reached a cap, the whole team was out of office, the record is waiting for working hours, or it matched no rule. These cases don't produce errors, so they hide inside the Not Routed and Delayed counts. Check them before changing any routing rule.

1. Caps without a fallback. Capping limits records per rep per day, week or month. When the chosen rep is capped or unavailable, a Fallback Owner (a user or a team via round robin) takes the record. With "No Fallback", it isn't assigned.
2. Everyone on vacation. Distro detects vacation from all-day busy blocks in reps' calendars and skips them in round robin. If every rep on the team is out, the record is not routed. Partial-day absences don't count.
3. Working-hours delays. "Delay Assignment Until Working Hours" holds a record until the assignee's schedule opens. That is correct behaviour, but it looks like a stuck lead to the person who submitted the form.
4. No Catch-all path. A record that matches no specific rule goes nowhere unless the router has a Catch-all. Add one that routes to a triage owner so nothing is silently dropped.
5. Trigger never fired. If the record isn't in the default view at all, show Not Triggered. Formula fields can't be used as triggers, and an update on a field the trigger doesn't watch won't start routing.
Section 08 · Reporting

Distro Logs vs Router Reporting vs Distribution Reporting: Which Do You Need?

Use the log for individual records, Router Reporting for router and path health, and Distribution Reporting for fairness between reps. The three views answer different questions. Teams that only check the log end up reading records one by one when a summary would show the pattern faster.

ViewWhereAnswers
Distro LogsDistro → LogsWhere did this record go, and why? Which records failed?
Router ReportingDistro → Router ReportingHow many records each router and path triggered and routed, the percentage routed, who is next in rotation, and each member's current level
Distribution ReportingReporting → Distribution ReportingHow many round-robin records each rep received or had reassigned, and who changed the distribution settings
Salesforce reportsThe Distro for Salesforce packageRouting fields such as Distro Assigned and Last Distro Route, for dashboards alongside your pipeline

The Distro for Salesforce package adds those routing fields to Leads, Contacts, Accounts, Cases and Opportunities, with a "Chili Piper Distro Reports" folder. It is the simplest way to put routing results in front of sales leaders who never open Chili Piper.

Section 09 · Routine

How Should RevOps Review Distro Logs Each Week?

Spend about 15 minutes a week on a fixed pass: errors first, then No Match patterns, then fairness. Routing problems rarely announce themselves. A broken connection or an over-strict rule can quietly cost leads for days. A short, regular review catches them before sales does.

  1. 1

    Scan the router list. Look at not-routed counts on active routers and confirm that routers you expect to be live are active.

  2. 2

    Clear errors. Filter Status to Error for the last 7 days, fix the cause in Salesforce or the router, then re-route or retry each record.

  3. 3

    Group No Match records. Open a handful and compare their Record Evaluations. If the same empty field keeps appearing, fix the form or add enrichment rather than patching records one at a time.

  4. 4

    Check fairness. Use Assigned To and Router Reporting to compare volumes per rep against caps, weights and vacation.

  5. 5

    Test changes before publishing. Run a real Lead or Contact ID through Preview mode, which runs the flow without updating Salesforce. If a change misbehaves, restore the previous version from Version History.

Section 10 · In Practice

What Makes Lead Routing Hold Up Over Time?

A clean CRM model underneath the router. Chili Piper carries out the routing logic it is given. If account ownership, territories or required fields are wrong in Salesforce, the log will faithfully record wrong decisions. Chili Piper's own error list makes the same point: most routing failures start in Salesforce data, rules or permissions, not in Chili Piper itself.

  • Match before you rotate. Send leads from existing customers to the account owner with lead-to-account matching, and keep round robin for genuinely new prospects.
  • Route on workload, not just turn order. For a UAE luxury real estate group, we built routing that assigns each inbound enquiry by property type, region and live workload, as part of a wider Salesforce program. Read the sales operations and lead management case study.
  • Make failure visible. Give every router a Catch-all and a fallback owner, so a record that can't be matched lands in a queue someone works, not in a log no one reads.

If you are setting up routers from scratch, our earlier walkthrough on routing Salesforce records with Chili Piper Distro covers rules, teams and routers step by step, and five ways to do round-robin assignment in Salesforce compares the native options. Our Chili Piper implementation services and Salesforce Sales Cloud services cover the routing model and the CRM underneath it.

Section 11 · Bottom Line

The Bottom Line

Chili Piper Distro Logs turn routing from a black box into something you can check. Used every week, the log shows you which leads failed and why, whether reps get a fair share, and which Salesforce limit or rule is quietly in the way.

  1. 1

    Open Distro → Logs, start with active routers that have a high not-routed count.

  2. 2

    Read the status first: Error, No Match and Delayed each need a different fix.

  3. 3

    Use the Record Evaluation's Data column to find missing or unexpected values.

  4. 4

    Fix push topic, Streaming API, validation and permission issues in Salesforce, then re-route.

  5. 5

    Add Catch-all paths and fallback owners so no lead disappears quietly.

Ready to Start

Get Every Inbound Lead to the Right Rep

On a 30-minute discovery call, a Twopir consultant will look at how your Chili Piper routers and Salesforce data work together, explain what your Distro Logs are telling you, and recommend the fixes that matter most.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Open the Distro section in Chili Piper and click Logs in the left-hand navigation. You see a list of CRM routers with their status, trigger object, trigger type, and records routed and not routed in the last 24 hours. Select a router to see the individual records it evaluated.

Admins and Workspace Managers. Distro features, including the logs, are available on Chili Piper's All Products and Routing & Scheduling plans. Reps don't need log access; they receive the assignment in Salesforce and, if configured, a Slack or email notification.

No Match means the record failed record evaluation or did not match any route, so it was not assigned. Open the record and expand its Record Evaluation: an empty or unexpected value in the Data column usually shows the cause. A separate status, No Match to Entry Rule, means the router's entry rule blocked the record.

Not Triggered and Discarded by Delay records are hidden by default. Select them in the Status filter to see records that did not meet the trigger criteria, or that were updated while already waiting to be routed.

Yes. Records that errored during routing can be retried with the Re-Route this record button, and failed CRM actions show a Try Again button for Admins and Workspace Managers. Fix the underlying cause first, such as a validation rule or a missing permission, or the retry will fail again.

Distro listens for Salesforce changes through push topics, and each Salesforce edition has a limited allocation. When it runs out, Distro cannot create the topics it needs. Delete unused push topics, for example in Workbench, or raise the allocation with Salesforce.

Distro's documentation covers Salesforce objects, triggers and limits only. Chili Piper integrates with HubSpot for other routing and scheduling features, so if your CRM is HubSpot, confirm with Chili Piper which product handles your routing before planning around Distro Logs.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Chili Piper routing on Salesforce.