⌘K
Amy Egan Please refer to the documentation for more details. There is an Ask AI feature available to help you vercel.com/docs
Juanclases33 5979 Thanks, Amy. I followed your suggestion: I read the relevant documentation and asked the docs' Ask AI about each unresolved point. Its answers did not identify a documented source that settles the distinctions below. I am not treating an AI answer as an official confirmation of unavailability. Could a Vercel team member answer these six numbered questions, or route the runtime/history questions to the relevant product team? The current single-human Owner role/count is already resolved. **1. Direct versus inherited access on Hobby** The Hobby comparison lists RBAC as N/A, and project-level roles are Enterprise-only. Does this mean that separate direct-project and inherited-team membership categories are **not applicable** to a single-Owner Hobby project? If they are applicable, how is that Owner classified, and which supported source defines the counts? Please distinguish effective permissions from stored assignments. **2. Overlap** If those categories apply, can the same Owner belong to both? Is there a supported aggregate source or documented rule for determining the overlap without publishing identities? If overlap is not applicable on Hobby, that explicit answer is sufficient; I do not want to infer zero from an unavailable UI. **3. Historical runtime version** The Node documentation explains automatic minor/patch updates and that build and runtime versions may differ. If an old invocation did not log `process.version`, is there any supported read-only record of the exact runtime minor/patch for an existing deployment, region and past timestamp? If yes, which source/field and retention? I am not asking for a pinned version, a new invocation, or the build-time version. **4. Installed function artifact** Does a customer have a supported read-only source for an immutable digest/manifest of the function artifact actually installed for an existing deployment? List Deployment Files describes source files, not that installed output. If the installed-output identity is not exposed to customers, please confirm that specific limit. **5. Provenance of that artifact** Is there a supported retained record linking that installed output to its source commit, resolved dependencies, build, deployment, environment and timestamp? Deployment metadata and build logs provide some of those facts; is the complete linkage available, and which parts are not covered? No environment-variable values or secrets are requested. **6. Past non-Fluid duration** The legacy guidance confirms the 10-second Hobby default without Fluid. For the original non-Fluid context on 11 October 2026, does a blank project Max Duration field with placeholder 10 establish that default, or can another setting override it? What retained source establishes the configured/applicable value at that time when the project response omits the relevant keys? The Activity Log lists `project-function-max-duration` and `project-functions-fluid-enabled/disabled`; GET /v3/events supports `withPayload=true`. Do these specific payloads include old/new settings, and what retention applies? Our earlier filtered read did not supply a historical value, so repeating it without a new reason would not settle this. **A short answer per number is enough:** applicable/not applicable; exact supported source and field if available; known coverage/retention limit. “Not customer-accessible” is useful. If internal retention cannot be confirmed, please say so rather than equating it with “not retained” or “impossible to reconstruct.” Partial answers are welcome. This remains a general, read-only capability question on Hobby: no account/project identifiers, private logs, attachments, upgrades, paid services, invocations, deployments or configuration changes are requested. Thank you.
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Pasha Thank you for the reference. I checked the suggested article, but I believe our issue is different from a typical deployment or website routing 404. The error occurs when the existing Vercel Connector calls the Vercel REST API: GET https://api.vercel.com/v2/user Response: 404 / not_found / User not found I have independently verified in the Vercel Dashboard that my account is an Owner of the relevant Team. The issue appears to involve the Connector's authorization principal or identity mapping, rather than a missing website page or deployment route. Could a Vercel Connect engineer or maintainer please review this specific case? In particular, I would appreciate guidance on how to diagnose the existing Connector's principal mapping and authentication context without replacing credentials or changing the current Team membership. Thank you.
