“Cached version not available, attempting to upload file.”
What does this warning message mean? What is being “cached”? What file is being uploaded, and to where?
Workflow keeps track of what Templates, DM Configs and Job/Output Presets it already sent to Connect. It does so by recording all upload operations in a cache, which is cleared each time you stop/resume the service. If it can’t find one of these resources in its cache, or if the resource is more recent than the one in the cache, it logs that message and uploads the most recent version of the resource to Connect prior to executing the requested operation.
Uploaded files are stored in the Connect FileStore, which is itself managed by the Server and its Cleanup service. From time to time, when a resource has not been used in a while and is no longer referenced by any job in the database, the cleanup service will delete some resources, which will prompt Workflow to upload its version once more.
This system maintains resource integrity while ensuring that the Connect FileStore does not contain tons of resources that are no longer being used.