<not reported> - This action expired before it could be executed

Reporting
1

Hi all how are you?

Have you ever had problem like this? The actions get stuck in until it expires. I was testing UDP and looks like it is enabled, i have activates the Command Polling also, but that did not help, the client is really slow and don’t execute patch actions. I see this on some actions summary:

This action expired before it could be executed.

Status Expired
Start Time Not Executed
End Time Not Executed
Exit Code None

In the logs i can see something like:
At 10:46:58 -0300 - mailboxsite (http://ip:52311/cgi-bin/bfgather.exe/mailboxsite1187085)
Downloaded ‘http://ip:52311/mailbox/files/5e/4f/5e4fc44e27e1ebcfc5be0fdd95ecd2b28a7f5574’ as 'Action 681384.fxf’
Gather::SyncSiteByFile adding files - count: 1
At 10:46:58 -0300 -
Successful Synchronization with site ‘mailboxsite’ (version 426) - 'http://ip:52311/cgi-bin/bfgather.exe/mailboxsite1187085’
Processing action site.
At 10:46:59 -0300 - mailboxsite (http://ip:52311/cgi-bin/bfgather.exe/mailboxsite1187085)
BackgroundAdviceEvaluation::FinishDataLoop side line file Action 681384.fxf

Nothing after that, in some other occasions i see:
DownloadsAvailable: false (action id 681394)

Have you ever had such a problem?

2

How long are you allowing between taking an action, and having the action expire?
Is the client’s date & time correct?
How large are the downloads?

3

An action can only be sidelined if it is not relevant and cannot become relevant without the agent restarting; like when the OS or hostname doesn’t match, or it is already expired. So it seems you’ve targeted this endpoint with an action that will never be applicable. Normally, that would still report Not Relevant, except in the expired case. What is the End Date/Time of the action, and is it specifying Local Time or UTC time?

4

The downloads are not that large, about 200mb (all patches combined). In a 9 hour window we do not get any updates.