community-support
Large files before/after deploy
v3
How do I go about installing an npm package that a task can use?
v3
Graphql support
Setup
v3
Using t3-env with Trigger.dev
Setup
v3
fsevents
v3
Internal monorepo package not resolved by Trigger
v3
Why are my logs showing in dev but not staging/production?
v3
Error: ServiceValidationError while deploying trigger to prod
v3
Prisma tracing errors
v3
max duration error
v3
Can't trigger tasks, sometimes ...
v3
useRealtimeRun onComplete never fires
v3
Deploy fail with new prisma --sql option
v3
Self-Host Trigger.dev Task stays in "Queued"
Self-hosting
TASK_RUN_HEARTBEAT_TIMEOUT
v3
Self-hosting
Puppeteer and Proxy Question
Setup
External fetch failures
v3
Issue with circular dependencies in a PNPM workspace
v3
Tasks not processed on Cloud
v3
Tasks are not queuing in prod
v3
Can't get Trigger API keys
Setup
v3
Self-hosting
Are extensions active for all tasks?
Setup
process.env.TRIGGER_ENV exists?
v3
GitHub Actions Failing
v3
Permission Denied for flyctl Installed via Build Extensions
v3
Nextjs integration with Trigger.dev
v3
Dependencies update is weird in monorepo
Setup
v3
Best way to filter runs by a custom workspace ID?
Setup
Getting error while using with prisma
Setup
v3
Build failed in new project, mac os, all packages required installed
Setup
Bug when testing tasks
v3
Environments Overwriting Each Other..?
v3
ApiConnectionError [TriggerApiError]: Connection error when tasks.trigger
v3
Self-hosting
Queues are not processed after deployment
Setup
v3
Self-hosting
Weird Task Execution... ran for 4 hours?
v3
Websocket error / Queue not working
Setup
v3
Self-hosting
Hi guys, could I use trigger.dev with prisma and sqlite, instead with postgresql??
v3
Rendering issue with useRealtimeRunsWithTag
v3
Metadata not being returned properly in runs endpoint
v3
Batch, random runs stuck
v3
Github Actions requests login
v3
Self-hosting
Trigger thinks it's still executing, even after completion
v3
Deno.js and import triggerdev v3
v3
422 "Cannot trigger integration-action as it has already been triggered with the same idempotency ke
v3
Supabase RLS with "task"
Setup
v3
#1 ERROR: unavailable: Unable to acquire machine, please retry
v3
toolTask Invalid payload
v3
How to clear trigger build cache?
Setup
v3
Tasks run when using `Test` functionality, but not when triggered from backend
v3
Retrieve child runs from root using PublicAccessTokens
v3