Answer
A full restart of both the database and IFS resolved this in practice: shut down IFS, reboot the database server, then start IFS again — after that sequence, the Admin Console's Deployments section correctly showed proper status again. The underlying cause of the 'getCurrentState' error itself wasn't identified, so this is a working recovery step rather than a root-cause fix, but it's worth trying before escalating further if the application is otherwise running normally for end users.