I know this shouldn't be necessary, but the lack of logs in saveToDb is clear - sometimes (probably when running multiple instances) a discord error isn't handled and breaks the job - before saving to elastic. By just sending the message to after the index/update operation is done this error won't silently fail
I know this shouldn't be necessary, but the lack of logs in saveToDb is clear - sometimes (probably when running multiple instances) a discord error isn't handled and breaks the job - before saving to elastic. By just sending the message to after the index/update operation is done this error won't silently fail