In case you need to track configuration issues to understand why a system suspends or does not, the extensive logging output of might be used. Each iteration of the daemon logs exactly which condition detected activity or not. So you should be able to find out what is going on. The command line flag autosuspend -l allows specifying a Python logging configuration file which specifies what to log. The provided systemd service files (see systemd-integration) already use /etc/autosuspend-logging.conf as the standard location and a default file is usually installed. If you launch manually from the console, the command line flag autosuspend -d might also be used to get full logging to the console instead.
In case one of the conditions you monitor prevents suspending the system if an external connection is established (logged-in users, open TCP port), then the logging configuration file can be changed to use the broadcast-logging package. This way, the server will broadcast new log messages on the network and external clients on the same network can listen to these messages without creating an explicit connection. Please refer to the documentation of the broadcast-logging package on how to enable and use it. Additionally, one might also examine the journalctl for after the fact.