-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Issues moving from mastra cloud #15259
Copy link
Copy link
Open
Labels
CLIIssues regarding Mastra CLI commands: Build, Dev, Start etcIssues regarding Mastra CLI commands: Build, Dev, Start etcDeploymentIssues with deploying to Mastra to [X] providerIssues with deploying to Mastra to [X] providerbugSomething isn't workingSomething isn't workingdiscordFor issues created from Discord discussions.For issues created from Discord discussions.effort:highimpact:hightrio-wp
Description
Metadata
Metadata
Assignees
Labels
CLIIssues regarding Mastra CLI commands: Build, Dev, Start etcIssues regarding Mastra CLI commands: Build, Dev, Start etcDeploymentIssues with deploying to Mastra to [X] providerIssues with deploying to Mastra to [X] providerbugSomething isn't workingSomething isn't workingdiscordFor issues created from Discord discussions.For issues created from Discord discussions.effort:highimpact:hightrio-wp
This issue was created from Discord post 1492267058619093032:
Server deploy consistently fails with 500 at upload step
CLI version: 1.5.0 @mastra/core: 1.24.1 Project ID: 099eb285-1a5c-43db-89f9-b90948b69ef1 Org: org_01KNTNDAMA0J7C6H3E3FNAMJYS
Running mastra server deploy --yes fails every time at the upload step with Error: Deploy failed: 500. The build completes successfully, the archive is created (4.4MB, 29 env vars), but the upload to the platform returns a 500.
I've tried:
Multiple retries (5+)
Cleaning up env vars (removed large tokens)
Updating all @mastra packages to latest
Running with DEBUG=*
mastra studio deploy works perfectly and is live at gamma-core-mastra03.studio.mastra.cloud -- same build artifact, same env vars. The issue seems specific to the server deploy upload endpoint.
Any known issues, or anything I can do on my end?