`endedAt` for Boundary Events

[MaheshkumarSundaram]

Hi @ralphhanna

Issue: endedAt for a Boundary Event is null instead of the actual end date & time after it's execution.

Expected Behaviour: endedAt should have an actual end date & time after it gets executed

Actual Behaviour: endedAt is null after it gets executed

Example:

Here, you can see the boundary timers get executed. But their endedAt value for the items are null in MongoDB.

But, in the other case

Here the boundary timers are not executed or cancelled. In this case, endedAt values for the items have actual date & time.

Could you please look into this?

Thank you.

[ralphhanna]

Fixed in release 1.3.28

• Item 4 & 5 : were executed and ended -with end timestamp
• Item 6: was executed - but cancelled - without timestamp

[ralphhanna]

Thanks

[MaheshkumarSundaram]

Thank you @ralphhanna