Patching Action not Expiring

[Aram]

Please see this post for more information on this:

Client local time action does not expire on schedule time

That’s actually normal behavior. The client will stop evaluating the action at the proper “client local time”. The Server and Console are not making assumptions about the local time zones of every client, and the action in the console won’t appear Expired until the specified time in the latest possible time zone. Suppose your console is in US Eastern Time, and you send an action to clients across the country to expire at “noon local time”. You wouldn’t want your your console to stop updating…

Or this:

Action stuck in "OPEN" state past Expiration Date!

(imported comment written by SteveHull) Hi Tim, The action will change to Expired later today, and this is intended behavior. The Server/Console will not show an action as Expired until the end time has passed in the last timezone (UTC-12:00). This is because the server doesn’t know which endpoints will end up being relevant for an action and/or what timezone that endpoint might end up being in. You are correct that an individual endpoint will still view the action as Expired if the time is…

Or this

Actions do not expire/move to "expired actions" at defined time

(imported comment written by Aram_Eblighatian) Amit, There is often confusion in this area since the expiration date/time behavior for actions may at first seem strange, but I will try to explain. The first thing to note is that as you suggest, an action’s start/end times are defined as client local time . Given this, it is very possible that you might have clients in timezones ‘behind’ that of the main BigFix server. So, actions remain in the ‘Open’ state until all possible client timezones…