chore: downgrade invalid connection data payload warn to debug

@zen-agentchecks n/achecks…zen/connection-data-payload-debug-gb7bnc → master1 files · +1 −1review: @rohanprabhureview: @sarthakreview: @acsrujanreview: @lingalarahul7review: @anshugarg15updated 3w ago

GitHub

▸Description· 1 comment · 6 noise

Description

Downgrade Invalid connection data payload warning to debug in apps/apollo/src/lib/connected_accounts/schemes/connectionDataScheme.ts.

This warning fires on every stored connection payload that fails the current Zod schema parse, but the function returns Ok regardless (lenient validation path). The sibling Mismatched status log in the same function is already at debug for the same reason.

Volume

99 occurrences across 5,000-log sample (~1.98%) of apollo-logs index (2026-05-18 windows: now, 2h, 6h, 12h, 24h ago).
All occurrences are warning level.

How did I test this PR

Ran grep -n "Invalid connection data payload" apps/apollo/src/lib/connected_accounts/schemes/connectionDataScheme.ts — confirmed level is now logger.debug.
Pure level change; no behavior or control-flow change in the function (still emits structured payload with errors field, still returns Ok lenient result).
Typecheck on the apollo package: see local run output.

Origin: cron-bdbff487aa80 / zen-cron-647c45e4d38c Triggered by: rahul.lingala@composio.dev | Source: cron Session: https://zen-api-production-4c98.up.railway.app/dashboard/#/chat/zen-cron-647c45e4d38c

@zen-agent3w ago

Post-PR follow-up complete (cron cron-bdbff487aa80 / zen-cron-647c45e4d38c)

/build-checks: ✅ PASS — pnpm lint (clean, 1 pre-existing warn on schemas.ts:1178 unrelated), pnpm format:check, pnpm check-types all green on apollo profile.
/codex-review-loop: ✅ "No issues."
CI: ✅ All 29 checks GREEN (last run elapsed 69s).
PR comments: none.
Testing: pure logger.warn → logger.debug swap on one line — no behavior, signature, or contract change. Lenient-validation function still returns Ok and attaches validationResult for caller inspection (verified by reading lines 1010-1050). E2E runtime test against Apollo not feasible — would require triggering schema-drift on a connection payload in prod. Apollo's apollo-logs Datadog index excludes @bunyan_level:<30 (debug), so the downgrade removes these from indexing entirely while preserving local debugging.
Ready for merge — awaiting review.

▸ 6 bot/status comments hidden

@vercel[bot]3w ago

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

Project	Deployment	Actions	Updated (UTC)
apollo	Ready	Preview, Comment	May 18, 2026 11:09am

Project	Deployment	Actions	Updated (UTC)
debby	Skipped		May 18, 2026 11:09am

@github-actions[bot]3w ago

🔍 Suggested Reviewers

Based on git blame analysis of 1 file(s):

Contributor	Contribution	Files
lingalarahul7	31%	1
Rahul Tarak

loading diff…

@zen-agent3w ago

Post-PR follow-up complete (cron cron-bdbff487aa80 / zen-cron-647c45e4d38c)

/build-checks: ✅ PASS — pnpm lint (clean, 1 pre-existing warn on schemas.ts:1178 unrelated), pnpm format:check, pnpm check-types all green on apollo profile.
/codex-review-loop: ✅ "No issues."
CI: ✅ All 29 checks GREEN (last run elapsed 69s).
PR comments: none.
Testing: pure logger.warn → logger.debug swap on one line — no behavior, signature, or contract change. Lenient-validation function still returns Ok and attaches validationResult for caller inspection (verified by reading lines 1010-1050). E2E runtime test against Apollo not feasible — would require triggering schema-drift on a connection payload in prod. Apollo's apollo-logs Datadog index excludes @bunyan_level:<30 (debug), so the downgrade removes these from indexing entirely while preserving local debugging.
Ready for merge — awaiting review.

Flag	Coverage Δ
e2e-tests	`6.06% <0.00%> (?)`
self-hosted-tests	`5.61% <0.00%> (ø)`
unit-tests	`58.68% <100.00%> (?)`

chore: downgrade invalid connection data payload warn to debug

Description

Volume

How did I test this PR

🔍 Suggested Reviewers

Description

Volume

How did I test this PR

🔍 Suggested Reviewers

💡 Recommendation

🧪 Test Results Summary (Self-Hosted Tests)

🧪 Test Results Summary (Unit Tests)

Codecov Report

🧪 Test Results Summary (E2E Tests)