New message in monitor? Reason: SUSPENDED_ON_CONDITION

[Lucinda_Mason]

Just want to make sure that this means what I think. In the past, if the condition wasn't met, nothing was shown in the monitor so it looked like the process didn't run. Now it appears to check every record, not sure what it selects as the initial data set, and then checks to see if it matches the condition. If it doesn't, it is logged as complete (seems weird) with a Reason: Suspended_on-Condition, then moves on to the next record. 

For processes that run and do what it is expected there is NO REASON stated. Can I have some explanation please?

[Steve]

Escalated.

[Zhifeng_Lin · Accepted solution]

Hi Lucinda,

There was an issue related to the monitoring app itself regarding the display of the "status"/"state" field (a new enum was incorrectly introduced, hence "suspended_on_condition" actually meant "completed"). A fix has been deployed to prod last Friday, but for bots that were executed during the breakage, their status/state have been incorrectly marked.

We put in another workaround in the monitoring app itself to account for the "incorrect" status/state based on the rough timestamp (2/23 to 2/25). But we did not make the same workaround to fix the "reason" column. (reason is displayed used when the bot is in pending state).

We just fixed the "reason" column as well.

Thanks!