I feel like this behavior only started happening recently — If you multiply a number A by a number B (that’s a funny type, but one that casts to string easily), you will get A out the other end; this is a sneaky failure and I would expect the automatic casting to take hold here, or to be warned that you’re multiplying two incompatible types.
I
(In my case the value in question is a Newtonsoft.Json.Linq.JValue — it casts just fine to number in any param expecting a number, but causes this failure in the Multiply components presumably due to its handling of many different data types)