Delivered in 20.18.02
The FootPrints 12 update should write to a new log file each time an upgrade is performed.
As it is now, subsequent upgrades append to the existing footprints_update_log.txt and can grow large rather quickly to hundreds of MBs and that causes issues transferring to Support etc.
Ideally, a new one should be created for each upgrade with a name footprints_update_log_yyyymmdd.txt.
For subsequent upgrades that may run on the same day, although somewhat unlikely, append a _n to indicate the run. Such as footprints_update_log_yyyymmdd_1.txt.