Fixlet's status is "Failed" yet all actions succeed

(imported topic written by SystemAdmin)


I have a simple fixlet that copies a policy doc from a precached BF location to a directory on a local disk. Every step of this very simple process succeeds, and the doc gets copied to a local directory, yet overall action result is “failed”, as seen below:

Status Failed

Start Time 5/21/2011 10:17:41 PM

End Time 5/21/2011 10:17:41 PM

Action Script Execution Detail

Completed download http://bfserver:443/Uploads/4b6c072929461d05037a89a7b93fad4cbe86d017/BackupPolicymht.tmp

Completed continue if {(size of it = 7915 AND sha1 of it = “4b6c072929461d05037a89a7b93fad4cbe86d017”) of file “BackupPolicymht.tmp” of folder “__Download”}

Completed extract SGHEBackupExemptionPolicymht.tmp

Completed copy __Download\BackupPolicy.mht c:\nobackup\BackupPolicy.mht

Has anyone seen this before? I’ve checked the local logs, there’s no indication of this particular action failing, it looks good in the log as well:

ActionLogMessage: (action 67198 ) Action signature verified

ActionLogMessage: (action 67198 ) Non-Distributed - DownloadsAvailable

ActionLogMessage: (action 67198 ) starting action

At 22:17:41 -0400 - actionsite (http://bfserver:443/cgi-bin/bfgather.exe/actionsite)

Command succeeded (Using download manager collected file) download http://bfserver:443/Uploads/4b6c072929461d05037a89a7b93fad4cbe86d017/BackupPolicymht.tmp (fixlet 67198)

Command succeeded (evaluated true) continue if {(size of it = 7915 AND sha1 of it = “4b6c072929461d05037a89a7b93fad4cbe86d017”) of file “BackupPolicymht.tmp” of folder “__Download”} (fixlet 67198)

Command succeeded extract BackupPolicymht.tmp (fixlet 67198)

Command succeeded copy __Download\BackupPolicy.mht c:\nobackup\BackupPolicy.mht (fixlet 67198)

At 22:17:41 -0400 -

ActionLogMessage: (action 67198 ) ending action

Thanks in advance!

P.S. This is on BF

(imported comment written by BenKus)

What is your “success criteria”?


(imported comment written by SystemAdmin)

Hi Ben,

Success criteria is “the applicability relevance evaluates to false” and I think maybe this is where the problem lies. I think I need to tune original relevance a little more as the current one is not working so well. Let me do that first and report back.