This names the FSM state this Downloader job was in immediately before its current one, again as a flattened summary property on the Downloader object itself. Comparing this to the current FSM status lets an admin see the download's last transition, for instance whether it just moved from connecting into downloading, which is useful for spotting a job that keeps bouncing back to the same earlier state instead of progressing. If the previous state was Local and the current one is also Local after a retry, that pattern signals the download step itself is repeatedly failing rather than progressing to validation.