Open gino-m opened 5 days ago
This exception occurs when the coroutine is cancelled via job.cancel()
or due to a timeout. It is automatically propagated to all it's child coroutines to cancel everything as expected. Therefore, we shouldn't be logging it as an exception.
On further debugging, I found that it happens when calling await()
if the job is already cancelled. So, handling this more gracefully will prevent this exception from getting thrown.
This has been logged in prod 319 times in the past 7 days. There are some potentially useful log lines under "Logs & Breadcrumbs", primarily related to: