Closed jgallen23 closed 9 years ago
When events go into something like good-mongodb, it errors out because we are logging the job class instance and it returns a max call stack size exceeded. Looks like we could just pass back the attrs
attrs
log { event: 'log', timestamp: 1418862364737, tags: [ 'agenda', 'complete' ], data: { agenda: { _name: undefined, _processEvery: 30000, _defaultConcurrency: 5, _maxConcurrency: 20, _definitions: [Object], _runningJobs: [], _jobQueue: [], _defaultLockLifetime: 600000, _db: [Object], _events: [Object], _processInterval: [Object], _nextScanAt: Wed Dec 17 2014 16:26:26 GMT-0800 (PST) }, attrs: { name: 'email-error-digest', data: {}, type: 'normal', priority: 0, nextRunAt: null, _id: 54921f1cef00780cf583b780, lastRunAt: Wed Dec 17 2014 16:26:04 GMT-0800 (PST), lastFinishedAt: Wed Dec 17 2014 16:26:04 GMT-0800 (PST), lockedAt: null }, _scheduled: true }, pid: 62732 } [RangeError: Maximum call stack size exceeded]
When events go into something like good-mongodb, it errors out because we are logging the job class instance and it returns a max call stack size exceeded. Looks like we could just pass back the
attrs