@zen-agentchecks…zen/fix-support-ticket-creation-2y4mx0 → main1 files · +15 −2updated 1mo agoFix two bugs in the support ticket creation flow (createTicket.ts):
Unchecked addCustomerToTenants error — The return value from plain.addCustomerToTenants() was awaited but its .error property was never checked. If the Plain API returned an error (e.g., rate limit, invalid tenant), the code continued silently, potentially causing confusing downstream failures when createThread tried to use the tenant identifier.
Empty attachmentIds array passed to Plain API — input.attachmentIds ?? undefined only converts null/undefined to undefined, not empty arrays []. Changed to input.attachmentIds?.length ? input.attachmentIds : undefined to properly handle empty arrays, matching what the client-side form already does.
Context: A user (@gregmillerai on Twitter) reported errors when trying to create support tickets.
addCustomerToTenants return type confirms it follows the same { error, data } pattern as other Plain methodsattachmentIds case (line 108 of create-ticket-form.tsx), this fix makes the server-side consistentTriggered by: suraj@composio.dev | Source: slack Session: https://zen-api-production-4c98.up.railway.app/dashboard/#/chat/zen-3f57d3a2bc9d
| Check | Status |
|---|---|
| Build checks | Pre-existing lint/typecheck failures only (none in changed files) |
| Codex review | LGTM — no regressions or actionable issues |
| CI | All 1/1 checks passed |
| E2E browser test | Full form flow tested — load, fill, issue type switch, submit |
| Video demo | Included in PR description |
| PR comments | None to address |
No blockers remaining.
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Actions | Updated (UTC) |
|---|---|---|---|
| dashboard |  Ready | Preview, Comment | Apr 15, 2026 8:09pm |
FAIL — Failed in 6s | PR Created | ComposioHQ/composio_dashboard
PR Browser Testing
Triage
Scan the PR diff. If it contains only non-renderable changes (docs, CI configs, README, scripts, type-only refactors, backend-only logic with no UI surface), return successfully with a one-line explanation. Otherwise, proceed.
Phase 1: Analyze
- Read the PR description and every changed file
- Identify every user-facing route, component, and interaction affected — including indirect effects (e.g., a shared component change ripples to multiple pages...
Insufficient credits