Error on doing "Find & recode"

Manager Edition: Desktop
Manager Version: 20.10.81
System: macOS Catalina 10.15.3

I’m getting this error when I click on “Find & recode” in the “Receipts & Payments” tab.

System.Collections.Generic.KeyNotFoundException: The given key '650a36fe-801f-4031-8d5b-ab422d061fca' was not present in the dictionary.
   at ManagerServer.HttpHandlers.Businesses.Business.ReceiptsAndPayments.FindAndRecode.InnerGet2() in C:\projects\manager\ManagerServer\HttpHandlers\Businesses\Business\ReceiptsAndPayments\FindAndRecode.cs:line 63
   at ManagerServer.HttpHandlers.Businesses.Business.BusinessTemplate.InnerGet() in C:\projects\manager\ManagerServer\HttpHandlers\Businesses\Business\BusinessTemplate.cs:line 327
   at ManagerServer.HttpHandlers.Template.Get() in C:\projects\manager\ManagerServer\HttpHandlers\Template.cs:line 281
   at ManagerServer.HttpHandlers.HttpHandler.ProcessRequest() in C:\projects\manager\ManagerServer\HttpHandlers\HttpHandler.cs:line 111
   at ManagerServer.Startup.<>c.<b__1_1>d.MoveNext() in C:\projects\manager\ManagerServer\Startup.cs:line 106
--- End of stack trace from previous location ---
   at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)

Including screenshot for reference.

Do you get this error when you first click the Find & Recode button or at some later stage of the process?

This happens as soon as I click the “Find & Recode” button.

I suggest updating your operating system. You should be able to update at least as far as macOS 10.15.7. I cannot reproduce this problem with macOS 10.15.7. Let us know if the problem persists after updating.

@shobhit, I just noticed you reported a different error with Find & Recode back in September that was related to employees assigned to custom control accounts. That was classified as a bug and was just fixed.

Is this new problem also fixed?

Yes, it is fixed now :slight_smile: Thanks so much!

Weird thing is that the previous issue had gone away somehow after a few updates since that post, so I assumed it was fixed and created a new topic thinking this to be some different problem. Anyways, everything is working well now!