fix(gmail): no-op thread-state write-backs when Google auth is missing

[KrisBraun]

Problem

PostHog issue 019ed581 — No Google authentication token available, 673 occurrences / 296 users in a week. (The issue's title is a stale PostHog grouping; the recent occurrences are all this Gmail error.)

The runtime dispatches onThreadToDo / onThreadRead to mirror to-do (star) and read state back to Gmail. Both resolved the API client via the throwinggetApiFn, which throws No Google authentication token available when a connection's Google OAuth has lapsed or been revoked. That throw is uncaught, propagates through the twist runtime, and pages error tracking on every to-do/read toggle for any re-auth-needed connection.

These write-backs are best-effort label syncs — the thread-state change already lives in Plot — so a missing token should degrade to a silent no-op, not an error.

Fix

• Add tryGetApiFn, a non-throwing variant of getApiFn that returns null when the channel resolves no token.
• onThreadToDoFn and onThreadReadFn now resolve the API via tryGetApiFn and return early (no-op) when auth is gone. In onThreadToDo the token is resolved before the local starred: mutation, so a no-token call is a complete no-op with no divergent marker left behind.
• The throwing getApiFn stays on user-initiated paths (onNoteCreated reply-send — which has its own deliveryError UX — downloadAttachment, listLabels), where a thrown error correctly surfaces to the user instead of silently flooding error tracking.

Tests

New TDD coverage in gmail.test.ts reproduces the production error (red), then passes after the fix (green):

• onThreadToDo / onThreadRead with no token → resolves without throwing, never calls Gmail.
• onThreadToDo with a token → still writes STARRED/INBOX (happy path unbroken).

Full Gmail connector suite: 53 passed · tsc --noEmit: clean · plot lint: clean.

No changeset (connector change, not twister/). No user-facing behavior change.

🤖 Generated with Claude Code

[KrisBraun]

Problem

PostHog issue 019ed581 — No Google authentication token available, 673 occurrences / 296 users in a week. (The issue's title is a stale PostHog grouping; the recent occurrences are all this Gmail error.)

The runtime dispatches onThreadToDo / onThreadRead to mirror to-do (star) and read state back to Gmail. Both resolved the API client via the throwinggetApiFn, which throws No Google authentication token available when a connection's Google OAuth has lapsed or been revoked. That throw is uncaught, propagates through the twist runtime, and pages error tracking on every to-do/read toggle for any re-auth-needed connection.

These write-backs are best-effort label syncs — the thread-state change already lives in Plot — so a missing token should degrade to a silent no-op, not an error.

Fix

• Add tryGetApiFn, a non-throwing variant of getApiFn that returns null when the channel resolves no token.
• onThreadToDoFn and onThreadReadFn now resolve the API via tryGetApiFn and return early (no-op) when auth is gone. In onThreadToDo the token is resolved before the local starred: mutation, so a no-token call is a complete no-op with no divergent marker left behind.
• The throwing getApiFn stays on user-initiated paths (onNoteCreated reply-send — which has its own deliveryError UX — downloadAttachment, listLabels), where a thrown error correctly surfaces to the user instead of silently flooding error tracking.

Tests

New TDD coverage in gmail.test.ts reproduces the production error (red), then passes after the fix (green):

• onThreadToDo / onThreadRead with no token → resolves without throwing, never calls Gmail.
• onThreadToDo with a token → still writes STARRED/INBOX (happy path unbroken).

Full Gmail connector suite: 53 passed · tsc --noEmit: clean · plot lint: clean.

No changeset (connector change, not twister/). No user-facing behavior change.

🤖 Generated with Claude Code

[KrisBraun]

Problem

PostHog issue 019ed581 — No Google authentication token available, 673 occurrences / 296 users in a week. (The issue's title is a stale PostHog grouping; the recent occurrences are all this Gmail error.)

The runtime dispatches onThreadToDo / onThreadRead to mirror to-do (star) and read state back to Gmail. Both resolved the API client via the throwinggetApiFn, which throws No Google authentication token available when a connection's Google OAuth has lapsed or been revoked. That throw is uncaught, propagates through the twist runtime, and pages error tracking on every to-do/read toggle for any re-auth-needed connection.

These write-backs are best-effort label syncs — the thread-state change already lives in Plot — so a missing token should degrade to a silent no-op, not an error.

Fix

• Add tryGetApiFn, a non-throwing variant of getApiFn that returns null when the channel resolves no token.
• onThreadToDoFn and onThreadReadFn now resolve the API via tryGetApiFn and return early (no-op) when auth is gone. In onThreadToDo the token is resolved before the local starred: mutation, so a no-token call is a complete no-op with no divergent marker left behind.
• The throwing getApiFn stays on user-initiated paths (onNoteCreated reply-send — which has its own deliveryError UX — downloadAttachment, listLabels), where a thrown error correctly surfaces to the user instead of silently flooding error tracking.

Tests

New TDD coverage in gmail.test.ts reproduces the production error (red), then passes after the fix (green):

• onThreadToDo / onThreadRead with no token → resolves without throwing, never calls Gmail.
• onThreadToDo with a token → still writes STARRED/INBOX (happy path unbroken).

Full Gmail connector suite: 53 passed · tsc --noEmit: clean · plot lint: clean.

No changeset (connector change, not twister/). No user-facing behavior change.

🤖 Generated with Claude Code

[KrisBraun]

Problem

PostHog issue 019ed581 — No Google authentication token available, 673 occurrences / 296 users in a week. (The issue's title is a stale PostHog grouping; the recent occurrences are all this Gmail error.)

The runtime dispatches onThreadToDo / onThreadRead to mirror to-do (star) and read state back to Gmail. Both resolved the API client via the throwinggetApiFn, which throws No Google authentication token available when a connection's Google OAuth has lapsed or been revoked. That throw is uncaught, propagates through the twist runtime, and pages error tracking on every to-do/read toggle for any re-auth-needed connection.

These write-backs are best-effort label syncs — the thread-state change already lives in Plot — so a missing token should degrade to a silent no-op, not an error.

Fix

• Add tryGetApiFn, a non-throwing variant of getApiFn that returns null when the channel resolves no token.
• onThreadToDoFn and onThreadReadFn now resolve the API via tryGetApiFn and return early (no-op) when auth is gone. In onThreadToDo the token is resolved before the local starred: mutation, so a no-token call is a complete no-op with no divergent marker left behind.
• The throwing getApiFn stays on user-initiated paths (onNoteCreated reply-send — which has its own deliveryError UX — downloadAttachment, listLabels), where a thrown error correctly surfaces to the user instead of silently flooding error tracking.

Tests

New TDD coverage in gmail.test.ts reproduces the production error (red), then passes after the fix (green):

• onThreadToDo / onThreadRead with no token → resolves without throwing, never calls Gmail.
• onThreadToDo with a token → still writes STARRED/INBOX (happy path unbroken).

Full Gmail connector suite: 53 passed · tsc --noEmit: clean · plot lint: clean.

No changeset (connector change, not twister/). No user-facing behavior change.

🤖 Generated with Claude Code

[KrisBraun]

Problem

PostHog issue 019ed581 — No Google authentication token available, 673 occurrences / 296 users in a week. (The issue's title is a stale PostHog grouping; the recent occurrences are all this Gmail error.)

The runtime dispatches onThreadToDo / onThreadRead to mirror to-do (star) and read state back to Gmail. Both resolved the API client via the throwinggetApiFn, which throws No Google authentication token available when a connection's Google OAuth has lapsed or been revoked. That throw is uncaught, propagates through the twist runtime, and pages error tracking on every to-do/read toggle for any re-auth-needed connection.

These write-backs are best-effort label syncs — the thread-state change already lives in Plot — so a missing token should degrade to a silent no-op, not an error.

Fix

• Add tryGetApiFn, a non-throwing variant of getApiFn that returns null when the channel resolves no token.
• onThreadToDoFn and onThreadReadFn now resolve the API via tryGetApiFn and return early (no-op) when auth is gone. In onThreadToDo the token is resolved before the local starred: mutation, so a no-token call is a complete no-op with no divergent marker left behind.
• The throwing getApiFn stays on user-initiated paths (onNoteCreated reply-send — which has its own deliveryError UX — downloadAttachment, listLabels), where a thrown error correctly surfaces to the user instead of silently flooding error tracking.

Tests

New TDD coverage in gmail.test.ts reproduces the production error (red), then passes after the fix (green):

• onThreadToDo / onThreadRead with no token → resolves without throwing, never calls Gmail.
• onThreadToDo with a token → still writes STARRED/INBOX (happy path unbroken).

Full Gmail connector suite: 53 passed · tsc --noEmit: clean · plot lint: clean.

No changeset (connector change, not twister/). No user-facing behavior change.

🤖 Generated with Claude Code

[KrisBraun]

Problem

PostHog issue 019ed581 — No Google authentication token available, 673 occurrences / 296 users in a week. (The issue's title is a stale PostHog grouping; the recent occurrences are all this Gmail error.)

The runtime dispatches onThreadToDo / onThreadRead to mirror to-do (star) and read state back to Gmail. Both resolved the API client via the throwinggetApiFn, which throws No Google authentication token available when a connection's Google OAuth has lapsed or been revoked. That throw is uncaught, propagates through the twist runtime, and pages error tracking on every to-do/read toggle for any re-auth-needed connection.

These write-backs are best-effort label syncs — the thread-state change already lives in Plot — so a missing token should degrade to a silent no-op, not an error.

Fix

• Add tryGetApiFn, a non-throwing variant of getApiFn that returns null when the channel resolves no token.
• onThreadToDoFn and onThreadReadFn now resolve the API via tryGetApiFn and return early (no-op) when auth is gone. In onThreadToDo the token is resolved before the local starred: mutation, so a no-token call is a complete no-op with no divergent marker left behind.
• The throwing getApiFn stays on user-initiated paths (onNoteCreated reply-send — which has its own deliveryError UX — downloadAttachment, listLabels), where a thrown error correctly surfaces to the user instead of silently flooding error tracking.

Tests

New TDD coverage in gmail.test.ts reproduces the production error (red), then passes after the fix (green):

• onThreadToDo / onThreadRead with no token → resolves without throwing, never calls Gmail.
• onThreadToDo with a token → still writes STARRED/INBOX (happy path unbroken).

Full Gmail connector suite: 53 passed · tsc --noEmit: clean · plot lint: clean.

No changeset (connector change, not twister/). No user-facing behavior change.

🤖 Generated with Claude Code

[KrisBraun]

Problem

PostHog issue 019ed581 — No Google authentication token available, 673 occurrences / 296 users in a week. (The issue's title is a stale PostHog grouping; the recent occurrences are all this Gmail error.)

The runtime dispatches onThreadToDo / onThreadRead to mirror to-do (star) and read state back to Gmail. Both resolved the API client via the throwinggetApiFn, which throws No Google authentication token available when a connection's Google OAuth has lapsed or been revoked. That throw is uncaught, propagates through the twist runtime, and pages error tracking on every to-do/read toggle for any re-auth-needed connection.

These write-backs are best-effort label syncs — the thread-state change already lives in Plot — so a missing token should degrade to a silent no-op, not an error.

Fix

• Add tryGetApiFn, a non-throwing variant of getApiFn that returns null when the channel resolves no token.
• onThreadToDoFn and onThreadReadFn now resolve the API via tryGetApiFn and return early (no-op) when auth is gone. In onThreadToDo the token is resolved before the local starred: mutation, so a no-token call is a complete no-op with no divergent marker left behind.
• The throwing getApiFn stays on user-initiated paths (onNoteCreated reply-send — which has its own deliveryError UX — downloadAttachment, listLabels), where a thrown error correctly surfaces to the user instead of silently flooding error tracking.

Tests

New TDD coverage in gmail.test.ts reproduces the production error (red), then passes after the fix (green):

• onThreadToDo / onThreadRead with no token → resolves without throwing, never calls Gmail.
• onThreadToDo with a token → still writes STARRED/INBOX (happy path unbroken).

Full Gmail connector suite: 53 passed · tsc --noEmit: clean · plot lint: clean.

No changeset (connector change, not twister/). No user-facing behavior change.

🤖 Generated with Claude Code

[KrisBraun]

Problem

PostHog issue 019ed581 — No Google authentication token available, 673 occurrences / 296 users in a week. (The issue's title is a stale PostHog grouping; the recent occurrences are all this Gmail error.)

The runtime dispatches onThreadToDo / onThreadRead to mirror to-do (star) and read state back to Gmail. Both resolved the API client via the throwinggetApiFn, which throws No Google authentication token available when a connection's Google OAuth has lapsed or been revoked. That throw is uncaught, propagates through the twist runtime, and pages error tracking on every to-do/read toggle for any re-auth-needed connection.

These write-backs are best-effort label syncs — the thread-state change already lives in Plot — so a missing token should degrade to a silent no-op, not an error.

Fix

• Add tryGetApiFn, a non-throwing variant of getApiFn that returns null when the channel resolves no token.
• onThreadToDoFn and onThreadReadFn now resolve the API via tryGetApiFn and return early (no-op) when auth is gone. In onThreadToDo the token is resolved before the local starred: mutation, so a no-token call is a complete no-op with no divergent marker left behind.
• The throwing getApiFn stays on user-initiated paths (onNoteCreated reply-send — which has its own deliveryError UX — downloadAttachment, listLabels), where a thrown error correctly surfaces to the user instead of silently flooding error tracking.

Tests

New TDD coverage in gmail.test.ts reproduces the production error (red), then passes after the fix (green):

• onThreadToDo / onThreadRead with no token → resolves without throwing, never calls Gmail.
• onThreadToDo with a token → still writes STARRED/INBOX (happy path unbroken).

Full Gmail connector suite: 53 passed · tsc --noEmit: clean · plot lint: clean.

No changeset (connector change, not twister/). No user-facing behavior change.

🤖 Generated with Claude Code