CapgeminiDCX AI Playground Hackathon 2026

Support

Stuck? Start here

Getting stuck is part of building. A useful first step is to work out what kind of blocker you’re hitting, capture the evidence, then try the smallest relevant fix. That makes self-service faster and gives a teammate enough context to help when you escalate.

A 60-second triage before you change anything

1 · Locate it

Is it access, install, build, browser, runtime/API, or Git?

2 · Capture it

Keep the exact command or URL, error, status, timestamp, and request ID.

3 · Isolate it

Change one thing and rerun the same check so you know what helped.

1. What kind of blocker is it?

Find the one that sounds most like you, then work through the steps.

Tool access

“It won’t let me in.” You can’t log in to v0, Vercel, GitHub, or Teams, or you don’t have a licence.

Try this yourself

  • Record the service, exact sign-in message, account used, and time of the failure.
  • Check the service-status links below before changing local settings.
  • Use a private window only to test whether cookies are the cause; do not bypass company SSO, VPN, or device policy.
  • If the error remains, confirm workspace or repository membership and ask the relevant owner to check access.

Tool know-how

“I’m in, but I don’t know how.” You have access, but you’re not sure how to prompt v0, push to GitHub, or deploy to Vercel.

Try this yourself

  • Choose one guide that matches your stack and complete its smallest working path before combining examples.
  • Check the installed package and runtime versions before copying code from a tutorial.
  • Ask an AI assistant with the relevant file, command, versions, expected result, and actual result — then review its diff and run the checks yourself.

Technical knowledge

“The code or concept isn’t clicking.” There’s an error you don’t understand, or you’re not sure how something works.

Try this yourself

  • Reproduce it once and classify where it fails: install, build, browser, runtime/API, or Git.
  • Capture the exact command or URL, actionable error, status code, timestamp, and request ID where available.
  • Change one thing, then rerun the same check. If needed, reduce the problem to the smallest failing input or file.
  • Before sharing logs with an AI or teammate, remove keys, tokens, cookies, personal data, and client information.

Idea or scope

“I don’t know what to build, or it feels too big.” You’re stuck on the what, not the how.

Try this yourself

  • Define one user, one problem, one outcome, and one happy-path demo.
  • Stub or remove integrations that are not needed to prove that path; use public or synthetic sample data.
  • Start from a current quickstart or template, then add one differentiating feature and one graceful failure case.

2. Quick fixes for common issues

Start with the middle column. The deeper check is there when the obvious fix does not explain the failure.

Deployment build fails

Start here

Open the failed deployment’s Build logs. The final “command exited” line is often only a summary — look just above it for the first actionable error, then run the same build command locally.

Go deeper

Compare the deployed commit, root directory, framework preset, Node version, package manager, and lockfile. Retry without build cache only when the evidence points to stale cache.

Live app errors or stays blank

Start here

Reproduce it once, note the time, then inspect the browser Network/Console and Vercel Runtime Logs. Match the route, HTTP status, deployment, and request ID.

Go deeper

Narrow the log time window; filter by environment, branch, deployment, route, and status; then search the request ID. Compare Preview and Production configuration and inspect failed outgoing requests.

AI calls fail

Start here

Capture the status and sanitized error from the browser Network panel, Runtime Logs, or AI Gateway request logs. Check authentication, model ID, rate or credit limits, and request size.

Go deeper

Handle both thrown errors and streamed `error` or `tool-error` parts. Use the Gateway request log and provider routing details to isolate the app, Gateway, or model provider.

Local dev command fails

Start here

Run `node -v` and `pnpm -v`, then `pnpm install` and the exact project script. Follow that project’s documented versions; the current AI SDK v7 quickstart requires Node 22+.

Go deeper

Run the production build and tests too. Keep the lockfile, and do not delete dependencies or caches until the error points there.

Environment variable missing

Start here

For local Next.js secrets, use `.env.local` and restart the dev server. In Vercel, add the variable to the correct Development, Preview, or Production scope and create a new deployment.

Go deeper

Verify the variable name and deployment scope — never share its value. `vercel env pull` can sync Development variables for local use.

v0 Git sync fails

Start here

Confirm the exact `owner/repo`, reconnect the intended repository, and check repository access under GitHub’s Installed GitHub Apps. An organisation owner may need to configure access.

Go deeper

Compare the Git remote, branch, commit SHA, and Vercel production branch. The Authorized GitHub Apps screen does not control repository selection.

AI output is wrong or inconsistent

Start here

Use a small input with a known answer. Inspect the prompt, retrieved chunks, tool inputs/results, and whether missing evidence is handled explicitly.

Go deeper

Create a repeatable evaluation set and change one variable at a time: model, prompt, retrieval, tool, or temperature. Compare results before keeping the change.

3. Still stuck? Ask for help

Post the smallest useful report, not a screenshot alone. Include what you expected, where it failed, the sanitized error, environment, last change, and what you tried. Redact keys, tokens, cookies, personal data, and client information before sharing. No question is too basic.

Expected result:
Actual result:
Where it fails: access / install / build / browser / runtime API / Git
URL or exact command:
Error text + HTTP status / request ID:
Environment: local / preview / production
Last working commit or last change:
What I already tried:

Remove all keys, tokens, cookies, personal data, and client information.
Ask in the Help channel

4. Let us know how it’s going

At the end of Week 1, take 30 seconds for the Pulse Check. It helps us spot where people are stuck and improve support. Its Microsoft Forms identity settings are managed by the organisers, so do not include sensitive information.

Open the Pulse Check

Looking for tools and links instead? See Resources.