# Identify which business rule acted on a conversation

> Identify which business rule acted on a conversation  When a conversation is updated by a business rule  for example when its marked Done or reassigned  you

Source: https://help.kustomer.com/en_us/identify-which-business-rule-acted-on-a-conversation-BytOikgRZl

Last updated: 2026-04-29T20:35:57.832Z

When a conversation is updated by a business rule — for example, when it's marked Done or reassigned — you can use audit logs to identify which rule made the change.

## **View audit logs for a conversation**

1.  Open the conversation you want to investigate.
2.  Select the ****Conversation Options**** menu (the three-dot icon in the upper right corner of the conversation).
3.  Select ****View Audit Logs****.

The audit log shows a timeline of all changes made to the conversation, including changes made by business rules and workflows. Each entry includes:

*   ****What changed**** — The attribute that was updated (for example, Status changed to Done).
*   ****Who made the change**** — If a business rule made the change, it displays the rule name.
*   ****When**** — The timestamp of the change.

## **Tips for investigating business rule activity**

*   ****Look for the rule name:**** Audit log entries from business rules reference the rule by name. Use the name to locate the rule in ****Settings > Platform > Business Rules**** and review its conditions.
*   ****Check for cascading rules:**** A single conversation update can trigger multiple business rules. If a rule applies a tag and another rule acts on that tag, both will appear in the audit log. Review the timestamps to understand the order of execution.
*   ****Review the spam flag:**** If a conversation was unexpectedly marked Done, check whether it was first marked as spam. A common cause is the system-generated __Auto-close & Filter Spam Conversations__ rule, which closes conversations flagged as spam. If the spam flag was set incorrectly, unmark the conversation as spam to prevent future occurrences.

## **Access audit logs via the API**

You can also retrieve conversation events via the API using the endpoint:

`GET /v1/conversations/{conversationId}/events`

To filter for automation-triggered events, include the query parameter `client=workflow` to identify workflow-triggered activity, or review event metadata for business rule references.

****Note:**** Audit logs are primarily a UI-driven feature. The events API provides activity data but does not have a dedicated audit log endpoint in the REST API.
