-
-
Notifications
You must be signed in to change notification settings - Fork 642
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: 3.1.11 does not handle maxDuration without configuration file? #1624
Comments
My trigger task clearly has the maxDuration param set. still i cannot run my trigger.dev
Trigger.dev (3.3.11)Key: Version | Task | RunX Error: The "maxDuration" trigger.config option is now required, and must be at least 5 seconds. |
I see, it needs to be set in the trigger.config.ts file too! |
I have it set and I still can't deploy: export default defineConfig({
// Your project ref (you can see it on the Project settings page in the dashboard)
project: "proj_xxx",
//The paths for your trigger folders
dirs: ["./trigger"],
logLevel: "log",
maxDuration: 7200, // 2 hrs Error:
|
This issue still persists, even after setting it in the trigger.config.ts and on the specific task. |
Provide environment information
When fully relying on the API endpoints version 3.3.11 does require a maxDuration which seems not possible to set in the "npx [email protected] dev" when not using a configuration file. Therefore I had to run instead this: "npx [email protected] dev --project-ref="proj_ijpicnzzxxxxtpvb" --skip-telemetry --skip-update-check.
Describe the bug
"npx [email protected] dev --project-ref="proj_ijpicnzzxxxxtpvb" --skip-telemetry --skip-update-check does not work without a configuration file due to maxDuration requirement?
System:
OS: macOS 15.3
CPU: (8) arm64 Apple M1
Memory: 155.09 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 23.5.0 - ~/.nvm/versions/node/v23.5.0/bin/node
Yarn: 1.22.22 - ~/.nvm/versions/node/v23.5.0/bin/yarn
npm: 11.0.0 - ~/.nvm/versions/node/v23.5.0/bin/npm
bun: 1.1.45 - /opt/homebrew/bin/bun
Reproduction repo
To reproduce
Additional information
No response
The text was updated successfully, but these errors were encountered: