Skip to main content
Editor logs serve as a comprehensive record of actions performed within the Encord platform’s Label Editor.

View Editor Logs

The following method is available on the Project class to retrieve Editor Logs. start_time and end_time are required parameters, while the rest are optional filters. /sdk-documentation/projects-sdk/sdk-activity-logs#object-actions
Use the following script to view Editor Logs for a specific project and data unit.

View Task Actions

Task actions can be retrieved using the following method on the Project class. after is a required parameter, while the rest are optional filters.
See the full list of task actions here.
The following script retrieves task actions for a specific Project and data unit, filtering for actions that occurred in the last 7 days.

Use Cases

Get History of a Label

Approval and Rejection Rates

The following script prints the approval and rejection rates for users in a Project.

Migrating from Activity Logs to New Editor Logs

Overview

Encord introduced a Editor Logs to replace the deprecated Activity Logs. The new logs are more structured, scalable, and aligned with how annotation actions are actually performed in the editor. Migrating to Editor Logs is not just a rename. Using Editor logs is a shift to a more structured, scalable logging system that better reflects real annotation workflows. After migration you will benefit from:
  • Faster queries
  • Cleaner filtering
  • More reliable audit trails
If you’re currently using the deprecated logs, this content will help you transition smoothly. Key Differences Conceptual Shift The biggest change is how logs are modeled: Before: Logs were general activity records (who did what, loosely defined) Now: Logs are editor events, tightly scoped to annotation actions Think of the new logs as a timeline of precise annotation events, not just audit entries.

SDK Migration

1. Replace Deprecated Log Calls Deprecated:
Editor Logs:
2. Update Filtering Logic Deprecated logs often required manual filtering after retrieval. Deprecated:
Editor Logs: Benefit: Reduced payload size and faster queries
3. Adjust to New Schema The structure of each log entry has changed. Deprecated:
Editor Logs:
Key Field Changes

Common Migration Patterns

Pattern 1: Tracking Label Creation

Before:
After:

Pattern 2: Filtering by User

Before:
After:

Pattern 3: Time-Based Queries

Before:
After:

Migration Checklist

  • Replace all get_activity_logs() calls
  • Update filtering to use server-side parameters
  • Refactor log parsing to new schema (event_type, actor, payload)
  • Validate downstream systems (analytics, dashboards, exports)
  • Remove deprecated logic and fallbacks

Tips and Tricks

  1. Event Granularity is Higher
You may see more logs than before because actions are more finely tracked. Plan for: Increased volume More precise filtering
  1. Payload Structure Varies by Event
Different event_types have different payload schemas. Recommendation:
  1. Pagination Matters
The new logs are designed for scale. Always handle pagination:
  1. Backward Compatibility
Deprecated logs will be removed. Do not rely on:
  • Old endpoints
  • Old schema fields

Example Migration

Before:
After: