There are separate background jobs showing up with the same trace ID
56a5b568c2bc7e48d528d682310b3c4d
These are completely different background jobs that are kicked off from different scheduled jobs. It's making it very hard to troubleshoot an error log.
6 Replies
Thanks for reporting this. The team will fix the issue in question
Thanks - it's a bug on the gadget side?
Pretty much all my error logs I've looked at today have the same trace ID so I'm kind of stuck trying to troubleshoot
Yes, this is an issue on Gadget's end. The issue is that background actions that are batches together are getting the same trace. A teammate is already on the issue
Thanks any ETA?
It has already been released
Are you still seeing issues?
looks like it's good now