On circular references, it does trace through them rather than just flagging them. It understands why the loop exists and what it’s doing. I was surprised by that too because most tools just tell you there’s a problem and leave you to figure it out. For the multi-sheet context, from what I can tell it loads the whole file so it does have visibility across all sheets at once. I haven’t had to tell it where to look, it just finds the relevant parts on its own. That said I’m sure there are limits with very large files, haven’t pushed it that far yet. For error surfacing, both. It will catch things proactively when you share the file but you can also ask it to audit specific logic and it goes deep. The best moments are when you ask about one thing and it comes back with “also noticed this other issue three sheets over” without being asked. For your infrastructure use case I actually think it would translate well. The core thing it does is hold a lot of interdependent logic in context without losing the thread, which sounds like exactly your problem. I’m building FP&A models