yes, it works here.
cutoff parameter and associated action are added by these lines in
 i’m able to reproduce that error by setting
engine.cutoff = 200 (or some other value,) which is an easy mistake but which overwrites the
.cutoff() method with a number and breaks it.
what’s odd is that after doing this, the error doesn’t go away, even after switching to a different engine and back. this seems to be a bug (i’d expect engine methods to be re-initialized.) will look into it.