Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B bull
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OptimalBits
  • bull
  • Issues
  • #453
Closed
Open
Issue created Feb 19, 2017 by Administrator@rootContributor

failedReason and stacktrace not in Queue.on('failed') and on('error') not triggering

Created by: alecl

Seems like these should be there given there's interested in the failures if you're handling the failed event, no? If I call Queue.getJob these two fields are there.

Also, I was surprised that Queue.on('error') doesn't get triggered whether I throw an error inside process or pass an error object to the callback. Looking at the code seems this even is mainly for Redis connection errors and not job errors?

Assignee
Assign to
Time tracking