Not really a way to check it.
The usual technique that other people are using for dynamic anomalies, is already using all the existing ones in the level, but just changing their position. You can try that approach if you feel you have reached a dead end.
Might want to litter the anomaly binders (and server entity class binders) with print statments. Make sure each function starts and ends. Sometimes undefined errors in engine cause script to just quit executing, that is why I have alun_utils.debug_write everywhere marking start and end. This particular error is especially bad if it happens to a script function bound to engine, such as the action planner, because it will call script over and over causing a stack overflow. Then you can just either manually look in log to inspect it's correct or use a clever regex in NPP or write a custom parser to detect such a thing in the log.
Place to start would definitely be anomaly save/load. If load is silently failing then object will be broken for sure. If there is no update, object is broken. etc.
"I have a dream that one day this community will rise up and live out the true meaning of its creed: "We hold these truths to be self-evident; that all mods are created equal."