Recurring exceptions in Octopus logs

Hey @prabhjotkour.91,

Sorry it has taken a while to get back to you on this one, I was discussing it with the rest of my team as I did think disabling that in the UI would mean it would not show in the logs (as you are no longer sending our telemetry data).

We do actually have a GitHub issue for this, I missed the bit in your picture where it mentions the given key was not present in the directory and was focusing on the 500 error.

That GitHub issue was generated from this forum post so you can see it is the same (the GitHub issue does not mention the 500 error but as you can see that user who posted up on our forum has the same 500 error you are seeing).

The issue is fixed in 2022.4.1657 so you would need to upgrade to that to stop it completely. For now, all users that are shown in your log will need to logout of Octopus, clear their cookies and cache on their browser and then log back in again. If you can upgrade to 2022.4.1657 or later though they will not need to do that.

The other ticket you posted up about your tasks not cancelling would also benefit from an upgrade to 2022.4 too so it might be worth seeing if you could do that to mitigate some of these issues you have found recently.

Hopefully that helps alleviate any concerns you had surrounding this issue, let me know if you have any further questions.

Kind Regards,
Clare