Board activity logs: cursor pagination and 90-day limit

Breaking change. In API version 2027-01, the activity_logs field on Board is rebuilt around cursor-based pagination, richer filters and a 90-day window. The field no longer returns a plain list of ActivityLogType entries. It now returns a BoardActivityLogsPage object that holds the page of entries and a cursor for the next page.

What changed for the activity_logs field on the Board type:

• New return shape. The field returns BoardActivityLogsPage with logs (a list of ActivityLog entries) and cursor (pass it back to fetch the next page; it is null on the last page). ActivityLog entries also expose correlation_id, triggering_flow_id and triggering_flow_type, which group entries that belong to the same logical session or triggering flow, such as an agent run.
• Cursor replaces page. The page argument is removed. Use the new cursor argument instead.
• New filters. event_types filters by event type (for example create_pulse), correlation_ids returns the events that belong to the same logical session, and search runs a free-text prefix search over item names.
• 90-day window. The from argument accepts timestamps up to 90 days in the past. A request for older data returns a validation error.
• Argument types changed. from and to are now String (ISO 8601) instead of ISO8601DateTime. column_ids and group_ids are now [ID!] instead of [String].
• limit default. The schema no longer declares a default value for limit. Its description states a range of 1-1000 and a default of 25.

Example request that reads the first page and the cursor for the next one:

query {
  boards(ids: [1234567890]) {
    activity_logs(
      from: "2027-01-05T00:00:00Z"
      event_types: ["create_pulse"]
      limit: 50
    ) {
      logs {
        id
        event
        entity
        user_id
        created_at
        data
      }
      cursor
    }
  }
}

Migration notes

If you query activity_logs on API version 2027-01, update your requests as follows:

1. Add the new selection structure. Select logs { ... } and cursor inside activity_logs { ... } instead of selecting entry fields directly.
2. Replace page with cursor. Send the cursor value from the previous response to fetch the next page, and stop when it is null.
3. Declare the from and to variables as String instead of ISO8601DateTime, and declare column_ids and group_ids variables as [ID!].
4. Keep from within the last 90 days. Requests for older data return a validation error.
5. If you generate types from the schema, regenerate them: the field now returns BoardActivityLogsPage.

Earlier API versions are not affected by this change in behavior. Their activity_logs field description now warns that the field changes starting from version 2027-01.