While I can tell you that in my case, I found the job causing the error by it's frequency, (the error was happening every five minutes) and there were only 2 jobs running every 5 minutes. However, after knowing which job was causing the error, I spent a lot of time to determine why the error was happening, given that the job itself was not failing.
Turns out that in the SQL Server Agent, Job Activity Monitor, Job Properties, Steps, (Edit), Advanced tab, someone checked the option: "Append output to existing entry in table", which caused that the output continued to grow over time, resulting in the error: "length of the result exceeds the > length limit (2GB) of the target large type". Unchecking the option circled below solved the issue for me.