#deploy preview

16 messages · Page 1 of 1 (latest)

exotic arch
#

I set CONVEX_TMPDIR and the deploy is successful "Deployed Convex functions" but when I look in dashboard there's no tables or functions - what is happening?

modest vineBOT
#

Hi @exotic arch. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

If your deploy preview is successful (shows "Deployed Convex functions") but you see no tables or functions in the Convex dashboard, there are a few common causes based on the knowledge sources:

  1. Schema File Naming Issue: Convex requires your schema file to be named exactly schema.ts or schema.js in the convex/ directory. If you accidentally named it something else (like schemas.ts), your tables will not be created, even though the deploy command succeeds. Double-check your file name and location. This is a common mistake and has caused similar issues for other users [Discord: Convex Schema].

  2. Wrong Deployment or Dashboard: Make sure you are looking at the correct deployment in the dashboard. Each preview deployment is separate and has its own data/functions. Use the dropdown in the dashboard to switch between deployments and ensure you are viewing the one just deployed [Dashboard Deployments].

  3. Schema Not Synced: If the schema file is correct but still not syncing, try restarting the deploy process and ensure there are no errors in the logs. Sometimes, issues with environment variables or the deploy process can cause the schema not to sync.

  4. Browser Cache/Extension Issues: Rarely, browser issues (like extensions or cache) can prevent the dashboard from updating. Try a different browser or clear your cache if the above steps don't resolve the issue [Discord: Dashboard not updating].

#

Summary:
The most likely cause is a misnamed schema file or viewing the wrong deployment. Double-check your schema file is named schema.ts and is in the correct directory, and ensure you are looking at the correct preview deployment in the dashboard. If the issue persists, try redeploying and check for any errors in the logs.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@exotic arch Kapa.ai is still learning and improving, please let me know how I did by reacting below.

exotic arch
#

@modest vine I see Deployed Convex functions to https://***.convex.cloud with no errors but there's no tables and no schema

modest vineBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

If you see the message Deployed Convex functions to <https://***.convex.cloud> with no errors, but there are no tables and no schema in the dashboard, the most likely cause is that your schema file is not named correctly. Convex requires the schema file to be named exactly schema.ts (or schema.js) and placed in the convex/ directory. If the file is named incorrectly (for example, schemas.ts), Convex will not pick it up, and your tables will not be created—even though the deployment appears successful. This has been confirmed as a common issue by other users [Discord: Convex Schema].

What to check:

  • Ensure your schema file is named schema.ts and is located in the convex/ directory.
  • After correcting the file name, redeploy your functions.

If the file name is correct and you still see no tables or schema, make sure you are viewing the correct deployment in the dashboard, as each deployment (including previews) is separate [Dashboard Deployments].

If you are still experiencing issues after these checks, there may be a more specific problem not covered in the knowledge sources provided.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@exotic arch Kapa.ai is still learning and improving, please let me know how I did by reacting below.

exotic arch
#

@modest vine which folder should be in CONVEX_TMPDIR?

modest vineBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

The folder you set in CONVEX_TMPDIR should be a directory on the same filesystem as your project directory (where your Convex project files, such as convex/_generated, are located). This is important because if the temporary directory (like /tmp) is on a different filesystem, you may encounter errors such as "cross-device link not permitted" during deployment or development. The folder should be writable by your user and exist before you run Convex commands.

For example, you might set it like this in your shell:

export CONVEX_TMPDIR=/path/to/your/project/tmp

Make sure /path/to/your/project/tmp exists and is on the same disk as your project directory. Setting CONVEX_TMPDIR in .env.local will not work; it must be set in your shell environment before running Convex commands [Discord: cross-device link not permitted].

If you continue to see issues, double-check that the directory is actually on the same filesystem as your project by using tools like findmnt or df.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@exotic arch Kapa.ai is still learning and improving, please let me know how I did by reacting below.

exotic arch
#

@modest vine so CONVEX_TMPDIR should point to _generated folder?

modest vineBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

No, CONVEX_TMPDIR should not point to your _generated folder.

According to the knowledge sources, CONVEX_TMPDIR should be set to a temporary directory that is on the same filesystem as your project directory (where your Convex files, including _generated, are located). It should be a separate, writable directory used for temporary files during Convex operations—not the _generated folder itself. For example, you might create a directory like tmp inside your project and set CONVEX_TMPDIR to that path:

export CONVEX_TMPDIR=/path/to/your/project/tmp

This helps avoid errors related to cross-device file operations during deploys or builds. The _generated folder is for Convex's generated code and should not be used as a temp directory [Discord: cross-device link not permitted].

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: