Templates submission returns HTTP 500 — request IDs and payload/thumbnail checks - Help

Hello and Vercel team — our public template submission consistently returns HTTP 500 with no actionable field error. Could a maintainer inspect the request IDs below and help us identify the smallest supported correction? We cannot tell whether this is a payload constraint or a submission-service failure.

Account: imomot-afk. Publisher: One Two Agent LLC. Template: Next.js SaaS Support with OneTwoAgent Repository: https://github.com/One-Two-Agent-LLC/nextjs-ai-customer-support-starter

GitHub

GitHub - One-Two-Agent-LLC/nextjs-ai-customer-support-starter: Next.js App Router starter for signed-in, account-aware OneTwoAgent support with scoped read-only backend access.

Next.js App Router starter for signed-in, account-aware OneTwoAgent support with scoped read-only backend access. - One-Two-Agent-LLC/nextjs-ai-customer-support-starter

Maintained demo: https://ota-northstar-demo.vercel.app Form: https://vercel.com/templates/submit

Latest controlled failure: 2026-10-07 20:49:29 UTC. POST https://vercel.com/api/templates/submit → 500 Internal Server Error. Exact JSON: {"error":"[/api/templates/submit] Error: Template submission failed.","ok":false} X-Vercel-Id: fra1:fra1:sfo1:sfo1:sfo1:sfo1:fra1:sfo1:sfo1:sfo1::iad1::w6xs4-1791406162260-8f1e87b12074 Earlier captured failure: 2026-10-07 20:18:19 UTC, same HTTP 500/JSON, duration 6.55 seconds. Earlier X-Vercel-Id: fra1:fra1:sfo1:sfo1:sfo1:sfo1:fra1:sfo1:sfo1:sfo1::iad1::pw5mh-1791404293420-f8ba2673a1b7 No field-specific error, success acknowledgement or submission ID was returned. Earlier attempts in another browser session also failed.

Reproduction: sign in with GitHub and complete Vercel 2FA; open the form; Check Repository succeeds; complete the template details, main branch, thumbnail, filters, build/install commands, environment variable names/docs and publisher details; submit through the official UI. The request reaches the submission endpoint and returns the error above.

Checks completed:

Public repository, App Router app, npm ci / production build, actual Deploy-button flow and maintained demo work.
Inspected the captured 23-field public JSON against the current public form schema. integrations=[] and integrationsOptional=false match its defaults. Framework=[next.js], type=[saas,ai,starter], database=[postgres,neon] are within current limits. Unselected optional filters are omitted. There is no Products submission field in the current form/schema; we did not invent one or modify requests manually.
Original thumbnail: valid 1440x1396, 177535-byte, 8-bit RGB non-interlaced PNG; only IHDR/IDAT/IEND chunks, valid CRCs, no EXIF or ancillary metadata. It meets the displayed aspect-ratio/minimum-height requirements. We found no documented 100 KB hard limit.
Exactly ONE additional controlled retry replaced only the thumbnail with a losslessly re-encoded metadata-free PNG (177020 bytes, identical pixels/dimensions). The complete public JSON remained identical. DevTools confirmed the new PNG filename/image/png in multipart. HTTP 500 persisted. We stopped further submissions.
We checked historical reports, without assuming the same cause: https://community.vercel.com/t/submitting-a-template-form-submission-failed-please-try-again/27681 (historical missing Products array, subsequently fixed) https://community.vercel.com/t/got-failed-to-upload-thumbnail-asset-when-trying-to-submit-the-template-to-vercel/2434 (thumbnail upload failures)

Please route this to the Templates team and inspect server logs for the request IDs, tell us the exact failing field/constraint or internal exception, and give the smallest supported correction. Also confirm whether any submission record was created despite the 500, and whether manual ingestion is possible if the form remains broken. We are not claiming this is an IP block or definitively your fault. No cookies, authentication headers, credential values or private customer data are included. We have already emailed Vercel Support; this public thread adds the diagnostics for the Templates team. Please reply here with the investigation result or the supported next step.

Hi there! I'm just a bot here to share some info that might help you before a human arrives.

If your account is eligible, you can use our new self-service recovery flow:

Go to vercel.com/login
Choose to sign in using the email + one-time password (OTP) option.
Select Use another sign-in method
Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account
Follow the remaining prompts to complete the recovery process

If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yourself. You can also use recovery codes if you've stored those in a safe place that you can still access.

If you are unable to access your account using the steps above, you can open a support case using the Start 2FA recovery option on the Two-Factor Authentication login screen. Please do not publicly post account details, like your email address, that could help an attacker gain access to your account in the future. There's no need to open an additional case if you already have one open.

Thanks for your patience while the team works to resolve all cases as quickly as possible while keeping everyone’s accounts safe and secure. A human should be here soon to help.