Operation Logs
6MM AI Customer Support · Tenant guide
Use operation logs to answer who changed what and when. Combine the action, target and source with the business record instead of reading the log description in isolation.
- Locate the event — Filter by time, keyword and category.
- Read the details — Check the actor, target, source and outcome.
- Verify the result — Open the affected record before retrying.
Trace an operation
Open Operation Logs. Filter by keyword, category, action, actor type, target type and date using the available controls. Read the details to identify who acted, which record changed and the result.
MCP operations are shown with their application/source and execution status. Depending on the operation, a business change and its MCP execution record can both appear; two audit entries do not by themselves mean the action was executed twice.
Distinguish authorization from execution
An application connection only proves authorization. A proposed write, a pending approval and a completed write are different states. The log is not a complete transcript of everything said to the external AI, and a read-only query should not be assumed to create a business-write record.
When investigating a failed MCP call, retain its operation ID, time and error message. Query the operation result before retrying. Operation logs are read-only through MCP.
Read one log entry
Example: an MCP article change did not appear
- Narrow the date range and look for the application or related operation.
- Check whether the operation is waiting for confirmation, failed or completed. Authorization alone does not mean the change executed.
- Open the target article and compare its current content. If a version conflict is reported, read the latest version and prepare a new request rather than reusing stale content.
- Preserve the operation ID and error details if further investigation is needed. A related business audit record and MCP execution record can describe the same change.
A useful handoff contains the time, target identifier, operation ID if present, and the observed result. It should not include account passwords or API secrets.
Common questions
Why is there no record for an AI conversation?
The operation log is not a transcript of chats in an external AI application. A read-only tool call also does not necessarily create a business change log.
Should I immediately repeat a failed-looking operation?
Check the operation result and target record first. If the client lost its response, the server may already have processed the request.