PR Summary

Medium Risk
Adds Redis-backed pagination caching into the tool executor and workflow execution cleanup paths; failures or Redis unavailability can change tool execution behavior and introduce new runtime dependencies/perf characteristics.

Overview
Adds an opt-in auto-pagination mechanism for tools: tools can now provide a pagination config, causing executeTool to automatically fetch subsequent pages, store each page in Redis, and replace the large output array with a lightweight paginated_cache_ref.

Introduces a new paginated-cache module (autoPaginate, hydrateCacheReferences, RedisPaginatedCache, types/tests) and updates block execution to transparently hydrate any cached references back into full arrays before downstream blocks run. Execution endpoints/streaming/queued execution now also clean up paginated-cache Redis keys (alongside existing base64 cache cleanup).

Updates Zendesk’s “Get Tickets” operation to use a new zendesk_get_tickets_v2 tool that supports cursor pagination and opts into the new pagination config; also extends test Redis mocks to support mget/scan.

^{Reviewed by Cursor Bugbot for commit 3fb6e34. Bugbot is set up for automated code reviews on this repo. Configure here.}

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 5, 2026 2:17am

Greptile Summary

This PR introduces a storage-agnostic auto-pagination framework for paginated tool outputs — pages are flushed individually to Redis as they are fetched, a lightweight PaginatedCacheReference is stored in block state instead of the full dataset, and downstream blocks transparently hydrate from Redis before execution. Zendesk get_tickets is the first tool to opt in, replacing the manual cursor UI with fully automatic multi-page fetching.

The architecture is well-designed (adapter interface, clean key schema, TTL safety-net, scan-based cleanup mirroring the existing base64 cache pattern) and the test coverage is solid. Two issues need attention before merge:

• Stale metadata.total_returned after pagination (paginate.ts): the return value spreads lastOutput, so metadata.total_returned reflects only the last page's item count rather than the cumulative total. After hydration, tickets contains all items but metadata.total_returned remains at the last-page value — downstream blocks that read this field will see incorrect data.
• apiToken visibility violation (get_tickets.ts): the Zendesk API token is declared 'hidden', which prevents users from entering it in the block UI. The project rule requires user-provided credentials to use 'user-only'.

Confidence Score: 4/5

Not safe to merge as-is — stale metadata.total_returned produces incorrect data for downstream blocks and apiToken: 'hidden' likely breaks the get_tickets UI.

Two P1 findings: (1) lastOutput spread causes metadata.total_returned to reflect last-page count only; (2) apiToken uses 'hidden' instead of 'user-only'. Both are straightforward one-line fixes. Infrastructure is solid.

apps/sim/lib/paginated-cache/paginate.ts (stale metadata) and apps/sim/tools/zendesk/get_tickets.ts (apiToken visibility)

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant BE as BlockExecutor
    participant TI as tools/index
    participant AP as autoPaginate
    participant RC as RedisPaginatedCache
    participant Redis
    participant HY as hydrateCacheReferences

    BE->>TI: executeTool(zendesk_get_tickets, params)
    TI->>TI: HTTP → page 0 result
    TI->>AP: autoPaginate(initialResult, params, config)
    AP->>RC: storePage(cacheId, 0, items)
    RC->>Redis: SET pagcache:page:{cacheId}:0 PX ttl
    loop while nextToken != null and pageIndex < maxPages
        AP->>TI: executeTool(toolId, nextParams, skipPostProcess=true)
        TI-->>AP: pageResult
        AP->>RC: storePage(cacheId, N, items)
        RC->>Redis: SET pagcache:page:{cacheId}:N PX ttl
    end
    AP->>RC: storeMetadata(cacheId, {totalPages, totalItems})
    RC->>Redis: SET pagcache:meta:{cacheId} PX ttl
    AP-->>TI: output with PaginatedCacheReference
    TI-->>BE: finalResult with cache ref
    Note over BE: Next block execution
    BE->>HY: hydrateCacheReferences(resolvedInputs)
    HY->>RC: getAllPages(cacheId, totalPages)
    RC->>Redis: MGET pagcache:page:{cacheId}:0..N
    Redis-->>RC: page data
    RC-->>HY: CachedPage[]
    HY-->>BE: inputs with tickets=[...all items]
    Note over BE: Workflow end
    BE->>Redis: SCAN pagcache:{executionId} then DEL

_{Reviews (1): Last reviewed commit: "auto-pagination with Redis cache for pag..." | Re-trigger Greptile}