Sometimes escalations execute high consuming time tasks, and until that tasks would not finish, the pool will not execute the next escalation.
If you active the log before it starts, you won't see activity in that pool. You'll see activity in the others pools.
Administrators need a way (using a command or whatelse) to know what escalation is being executed in this moment, and if whatever else information related to that execution BMC could provide (al least when it starts and the name, and the pool number of course).
Usually, a escalation pool that not appears in the log (during for example 30 mins.) is a symthom of something going wrong, but Administrator don't have tools to detect it, and we are very reactives with this.