PREP_PROCESS_FILE() function appears to return results out of cache rather than from disk at time of :PROCESS ing
Stale file contents were gathered using the PREP_PROCESS_FILE() script function. For example:
Results of the process command:
Release : 12.3
Component : Automation Engine
This is as designed
Automic should not pull from cache on the file system rather than from disk; this is something that would be handled from the Windows side rather than from Automic.
The behavior outlined Introduction above is as designed, caused by the prep_process_file function writing to the database when activated and the file being changed between prep_process_file being assigned
Scenarios where this could occur:
If there is a script in a workflow with generate at activation set and it's activated before the file is updated, it will take the file contents at activation, not at runtime
If the script has the prep_process_file command assigned (declared) early in the script before it's actually processed and the file changes between assignment and processing, it will take the file contents at assignment, not processing
The file contents that were for the specific run can be seen by right-clicking the task execution, choosing "Execution Lists" -> "Child Task Executions" and opening the report called something like PREP_PROCESS_FILE([task name],[10 digit run number of script execution]).