Google Drive (2026-05-18)

List Changes (and the New and Updated Files polling trigger that wraps it) now persists its Google Drive page token in crossFlowState keyed by context.flow.stableId and context.stepId so it survives deployments while keeping per-step page tokens when a flow contains multiple List Changes steps. Existing instance-state page tokens are migrated transparently on the next run, with no re-baseline