Sure it makes sense. I just somehow gotten the impression that this was something that would be handled by the TurboActivate wizard.
You can do that is you want, but you have to launch the TurboActivate wizard (that is, run the TurboActivate.exe). See the example C# code.
You might want to think about updating your guide for using Turboactivate with c# at (at https://wyday.com/limelm/help/using-turboactivate-with-csharp/) to at least mention the fact that this is an error that must be handled.
Well, if you're using C# then we recommend using the TurboActivate wizard, not using the Activate() function. But even if you use the Activate() function the exceptions it throws are shown.
In the near future we'll be adding an online API list show all possible exceptions and all the behavior. But right now it's in the code (e.g. for C# it's all in the TurboActivate.cs file).