So I have a customer who is unable to generate an exception that will trigger the try catch activity in workflow. They are on 9.1.1

They have this example SDK script:

        /// <summary>
        /// This method is run when the activity is performed.
        /// </summary>
        protected override void Execute()
        {
            try
            {
                  Do work and it fails!!!
            }
            catch (Exception e)
            {
                 // This error is caught and we throw the exception to the WorkFlow 
                throw new LaserficheException("Script threw exception", e);
            }
        }
    }

When they run this as part of a try-catch activity (shown above) it comes back as a a warning which skips the catch branch. We've gone into the catch settings and set it for anything and we've specified the actual exception. We've also tried switching it to one of the system exceptions the catch activity is aware of. 

The customer is aware of returning a token and using a conditional to then effectively do the same procedures that a catch would do but would prefer to "use the tools as they were designed", especially when he wants to potentially catch exceptions he didn't plan for. 

Anyone have any ideas?