Why did my Maximo escalation not fire, or fire too often?

Work through the checklist below. On our lab systems the error rows in the escalation run log carried no message text, and two of the loggers on IBM’s list were not there until created.

Versions: On Maximo Application Suite 9.1 we confirmed, read-only, the run log, the logger table, the property and the messages described here (17 November 2026), after reading the same on Maximo 7.6.1.2 (4 November 2026). Both checks were read-only: we did not run a failing escalation on either version. The checklist items come from the definitions and from IBM’s documentation.

IBM’s page: IBM’s current Maximo Manage documentation lists five escalation loggers: crontask (DEBUG), ESCALATION (DEBUG), sql (INFO), COMMTEMPLATE (INFO) and mail (DEBUG).

Last checked: 17 November 2026

How it works

Three places tell you what an escalation did:

  1. The escalation run log (table ESCSTATUS, shown in the Escalations application). One row per run result, with the status, the date, the number of records processed and a memo.
  2. Cron task history, but only where Keep History is on for the cron task instance.
  3. The logs. IBM’s escalation loggers: crontask (DEBUG), ESCALATION (DEBUG, a child of crontask), sql (INFO, the SQL actually run), COMMTEMPLATE (INFO) and mail (DEBUG). Set them in Logging, attach an appender, and click Apply Settings.

What we read on both systems: on Maximo Application Suite 9.1 and on Maximo 7.6.1.2 the run log held the same 17,675 ERROR rows, and not one of them had any message text. (The identical number suggests these rows came with IBM’s demonstration data.) So for the reason behind an error, expect to need the server log. The ESCALATION and COMMTEMPLATE loggers from IBM’s list were not in the logger table on either system; add them in the Logging application if you need them. We found no delivered job that clears the run log: an escalation that runs every 5 minutes adds about 100,000 rows a year.

Checklist

  1. Is it active? The escalation and its cron task instance must both be active. They can disagree.
  2. May cron tasks run on this server? Check the mxe.crontask.donotrun property.
  3. Does it select anything? Run the condition yourself as select count(*) from <object> where <condition>. Then add each escalation point’s condition and time test by hand.
  4. Validate it again. SQL errors show in the validation results.
  5. Read the run log, newest first. “0 records processed” means nothing qualified, not that it is broken.
  6. Turn on ESCALATION and sql at DEBUG for one run. Read the SQL the engine ran. Then set them back. On Maximo Application Suite the server log is a container log; IBM’s APIs for administrative utilities page describes how to download log files.
  7. For notifications: the communication template is active, the recipients resolve to real people with e-mail addresses, and a mail server is set.

Where it breaks

How we checked it

On a Maximo 7.6.1.2 lab system we read the escalation run log (grouped by escalation, status and memo), the escalation and escalation point conditions, the logger table and the escalation messages, all with read-only queries. We then read the same on a Maximo Application Suite 9.1 system. Nothing was changed on either.

Not tested: a failing run, the logger output, and running the Oracle-style conditions on Db2.

This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.