panic: Sentry detected 16 stuck task(s):
	Task tid: 11034 (0x2b1a), entered RunSys state 3m30.05s ago.
	Task tid: 30 (0x1e), entered RunSys state 3m30.01s ago.
	Task tid: 6 (0x6), entered RunSys state 3m1.56s ago.
	Task tid: 11 (0xb), entered RunSys state 3m29.98s ago.
	Task tid: 4627 (0x1213), entered RunSys state 3m1.56s ago.
	Task tid: 9 (0x9), entered RunSys state 3m1.56s ago.
	Task tid: 25 (0x19), entered RunSys state 3m29.94s ago.
	Task tid: 27 (0x1b), entered RunSys state 3m30.01s ago.
	Task tid: 2337 (0x921), entered RunSys state 3m30.01s ago.
	Task tid: 18 (0x12), entered RunSys state 3m30.01s ago.
	Task tid: 37163 (0x912b), entered RunSys state 3m42.23s ago.
	Task tid: 37162 (0x912a), entered RunSys state 3m42.19s ago.
	Task tid: 10 (0xa), entered RunSys state 3m30s ago.
	Task tid: 26 (0x1a), entered RunSys state 3m30s ago.
	Task tid: 5 (0x5), entered RunSys state 3m1.56s ago.
	Task tid: 2 (0x2), entered RunSys state 3m1.56s ago.
Search for '(*Task).run(0x..., 0x<tid>)' in the stack dump to find the offending goroutine
Stack for running G's are skipped while panicking.