Thanks for confirming this.
We were using integer and tried a couple tools including this to create a stop point in the middle of the model.
We noodled with it this morning and our model was using it to create a dissolved shapefile of selected parcels in a zipped file that is to be submitted (via upload) as an area of interest to online reporting tools created by other agencies.
Many of those have a minimum threshold (varies) of acres for the report to run.
When the user selects the parcels of interest they are copied into memory, dissolved, and then the combined area is calculated.
If larger than user defined minimum acres, then the tool proceeds. If less, then that is used as a precondition and the model stops.
The "If Value Is" tool worked for us when we finally used it in conjunction with the "Get Field Value" on the final dissolved feature create in the prior step.
Using that that previously calculated value to compare to the user defined minimum was the true false expression condition we wanted.
Connecting directly to that caused the odd behavior while inserting the Get Field Value too removed the hangups.
It has worked like a charm stopping/continuing the model this way.
I now need to add a meaningful message to the user when it completes the model or not.