The repeat being disabled causes Maximo to populate the record ID into the escrepeattrack table. This is how Maximo tries to ensure the record hasn't already been processed. I would be surprised if you had anything that removed entries from this table, but that would be where I would check to make sure the record you expect is being populated.
Assuming it is being populated, you should check that you don't have multiple escalation points (each controls its own repeat flag) or something else that might be updating the record.
------------------------------
Steven Shull
Naviam
------------------------------
Original Message:
Sent: 05-05-2026 16:30
From: Jason Johnson
Subject: Escalations
I have an escalation that has three "setvalue" actions (two YORN and a date/time of now()). The "Repeat?" flag is not set in the escalation point definition, but the actions are executed every time the escalation runs. The problem is the date/time is always updated. I thought once a record was touched by an escalation it gets ignored on subsequent runs.
Not sure if this has anything to do with it, but where clause dataset is the same every time (at least in my short 5-minute testing). But again, I thought it was a run-once mechanism when "Repeat?" was blank.
#Administration
------------------------------
Jason Johnson
RSI
------------------------------