When a job uses assets as inputs, and the asset doesn't already exist, and the specified file doesn't exist locally either, we end up with an asset created for which there is no content. This triggers errors in a job that will try to use that asset, or when trying to download the asset from the GUI.
When a job uses assets as inputs, and the asset doesn't already exist, and the specified file doesn't exist locally either, we end up with an asset created for which there is no content. This triggers errors in a job that will try to use that asset, or when trying to download the asset from the GUI.