#Task stays queued, never starts on local dev

1 messages · Page 1 of 1 (latest)

plush zenithBOT
#

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

#

I apologize, but based on the knowledge sources provided, I don't have enough specific information to address why your task is staying queued and not starting in local development. The documents available don't contain details about local development troubleshooting or queuing issues.

However, I can provide some general suggestions based on TriggerDev's functionality:

  1. Make sure you have set up your local development environment correctly according to TriggerDev's documentation.

  2. Check if you have properly initialized the TriggerDev client in your local setup.

  3. Verify that you're using the correct API key and other necessary configurations.

  4. Ensure that your local TriggerDev server is running and accessible.

  5. Check the logs of your local TriggerDev instance for any error messages or warnings that might indicate why tasks are not being processed.

If the issue persists, I recommend consulting the official TriggerDev documentation for troubleshooting guides or reaching out to their support channels for more specific assistance with your local development setup.

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

#

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

blissful cypress
#

My setup is a bit niche, it's astro running vite, i have hono running the following,

 
const routes = app
  .use('/trigger', createMiddleware(triggerClient()))

My trigger.config looks like the following

import 'dotenv/config'
import {defineConfig, configure} from '@trigger.dev/sdk/v3'

configure({
  secretKey: process.env['TRIGGER_SECRET_KEY'] // starts with tr_dev_ or tr_prod_
})

export default defineConfig({
  // Your project ref (you can see it on the Project settings page in the dashboard)
  project: '...',
  //The paths for your trigger folders
  dirs: ['./src/trigger'],
  maxDuration: 1 * 60 * 10, // 10 minutes
  retries: {
    //If you want to retry a task in dev mode (when using the CLI)
    enabledInDev: false,
    //the default retry settings. Used if you don't specify on a task.
    default: {
      maxAttempts: 3,
      minTimeoutInMs: 1000,
      maxTimeoutInMs: 10000,
      factor: 2,
      randomize: true
    }
  }
})
#

Pretty standard over all from what I could tell in the docs, but the task stays queued on one screen, and then it seems to have run on the other, or it never started. Any help, is running dev actually deploying the code? I wish there was more visibility into how trigger is running vis a vis the runtime/builds/compiles etc.

fiery ginkgo
#

You're running the CLI?

npx trigger.dev@latest dev

What does this do?

const routes = app
  .use('/trigger', createMiddleware(triggerClient()))
blissful cypress
#

it was code left over from the hono client, i removed that reading around that its deprecated, and tried to follow the docs very carefully it just seems outdated docs led me astray

little bramble
#

Same here on nextjs