Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Sales CRM · Feature guide

Review automation results and resolve skipped actions

Use the deal audit trail to understand what ran, why an action was skipped and when a fresh event is required.

Audience: authorised staffPermission: View access to the deal; Administrator to change rulesReviewed 30 October 2026
Where to goSales CRM → Deals → Open a deal → Automation activity and Deal history

Before you start

Use your own authorised staff account in the intended Britixo workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.

Follow these steps

  1. Open the deal and find Automation activity. Expand the relevant rule name and timestamp.
  2. Read every action result. Completed means the action was applied; Skipped includes its validation or permission reason.
  3. Compare the resulting activity, cadence, next step or forecast category with the intended outcome.
  4. If configuration needs correction, an administrator can edit the rule in Sales setup. Resolve deal or owner issues through normal authorised controls.
  5. After correction, make the intended new deal event when appropriate. Configuration changes alone do not rerun historical events.

Behavior and limits

  • The panel shows the ten most recent matched automation events. Non-matching rules do not produce an event entry. The general Deal history panel shows its latest 100 events.
  • An event key prevents the same recorded deal event from running twice. A genuinely new save can be a new event and may intentionally create another activity.
  • The event entry retains the rule name at execution and the action results. Later renaming a rule does not rewrite that entry.
  • A create-only user’s matching event records that Edit permission is missing. The rule does not acquire an administrator’s permissions.
  • A skipped action is not proof that every action failed. Review each result individually.
  • No automatic email, SMS, WhatsApp message or telephone call is sent by this event automation feature. Existing communication approvals and suppression controls remain applicable.

Check it worked

  • Check that the timestamp and rule name correspond to the deal event you intended to inspect.
  • Count generated activities against completed Schedule activity actions and check the detailed skip reasons.

Troubleshooting

  • No event entry can mean no active matching rule, a different trigger, an unavailable public field or that the entry is outside the latest-ten display.
  • If a repeated Save created another reminder, review whether the rule should be narrower or use a different trigger. Idempotency protects duplicate event processing, not every future save.
  • If a save reports a conflict, refresh the deal before trying again; do not repeatedly submit an outdated revision.
  • For support, provide the rule name, approximate time and displayed error, avoiding unnecessary customer or private field details.