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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 10, 2026 6:04am

PR Summary

Medium Risk
Adds new polling-based trigger execution paths (new cron jobs, provider handlers, and idempotency retry behavior) and extends trigger-mode rendering logic, which could affect workflow execution volume and UI visibility if misconfigured.

Overview
Adds new polling triggers for Google Calendar, Google Drive, and Google Sheets, including new poller trigger configs and polling provider handlers wired into POLLING_PROVIDERS, the polling handler registry, and the trigger registry, plus new Helm cron jobs to run the poll endpoints.

Updates block configs for Google Calendar/Drive/Sheets to expose these triggers in the UI by spreading trigger subBlocks and enabling the new trigger IDs, and regenerates integrations.json to list the new triggers.

Introduces a new sub-block mode trigger-advanced and updates editor/preview rendering, trigger config aggregation/deploy, copilot block metadata, canonical visibility grouping, and validation to treat trigger + trigger-advanced as trigger-only fields. Polling idempotency now supports retrying failures by deleting failed keys instead of caching them.

^{Reviewed by Cursor Bugbot for commit 9a33570. Configure here.}

Greptile Summary

This PR adds polling triggers for Google Sheets (new rows), Google Drive (file changes), and Google Calendar (event updates), wires them into the existing block configs, introduces a new trigger-advanced subblock mode for advanced canonical-pair fields in trigger context, and adds retryFailures support to the IdempotencyService. The polling handlers follow the established pattern from Gmail/Outlook, and the previous round of review comments (cursor revert on failure, timestamp guard, rate-limit handling, etc.) have all been addressed.

Confidence Score: 5/5

Safe to merge — all previously flagged P0/P1 concerns have been addressed; remaining findings are P2 style/quality suggestions only.

The cursor-revert-on-failure logic, timestamp guard for Calendar, rate-limit handling, and idempotency with retryFailures are all correctly implemented. The two remaining P2 comments (Drive 403/429 descriptive messages and Calendar no-op timestamp update) are non-blocking improvements that do not affect correctness or data integrity.

apps/sim/lib/webhooks/polling/google-drive.ts (rate-limit error messaging) and apps/sim/lib/webhooks/polling/google-calendar.ts (empty-poll timestamp update).

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Scheduler as Trigger.dev Scheduler
    participant Poller as Polling Handler<br/>(Calendar / Drive / Sheets)
    participant GoogleAPI as Google API
    participant Idempotency as IdempotencyService<br/>(retryFailures=true)
    participant Processor as processPolledWebhookEvent
    participant DB as Webhook Config (DB)

    Scheduler->>Poller: pollWebhook(ctx)
    Poller->>DB: read providerConfig (cursor / timestamp / rowCount)

    alt First poll (no state)
        Poller->>GoogleAPI: getStartPageToken / now.toISOString()
        Poller->>DB: seed initial state
        Poller-->>Scheduler: success (no events fired)
    else Subsequent poll
        Poller->>GoogleAPI: fetch changes since cursor/timestamp
        GoogleAPI-->>Poller: events / changes / rows

        alt No results
            Poller->>DB: update state (Sheets/Drive) or keep timestamp (Calendar)
            Poller-->>Scheduler: success
        else Results found
            loop for each event/change/row
                Poller->>Idempotency: executeWithIdempotency(key, operation)
                alt Cache hit (completed)
                    Idempotency-->>Poller: cached result (no re-fire)
                else Cache hit (failed) + retryFailures=true
                    Idempotency->>DB: delete failed key
                    Idempotency->>Processor: re-execute operation
                else First time
                    Idempotency->>Processor: execute operation
                    Processor-->>Idempotency: success / failure
                end
            end

            alt Any failures
                Poller->>DB: revert cursor/timestamp/rowCount
            else All success
                Poller->>DB: advance cursor/timestamp/rowCount
            end
            Poller-->>Scheduler: success or failure
        end
    end

_{Reviews (11): Last reviewed commit: "fix(polling): advance calendar cursor pa..." | Re-trigger Greptile}

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review

@greptile

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review