Optimization
Re-running optimization
Reprocess assets under new settings.
Optimization applies to assets as they're processed. Changing a profile, upgrading a plan, or adding a folder does not retroactively reprocess anything — you re-run it deliberately.
When re-running makes sense
You changed the profile. The new balance applies going forward; existing assets keep whatever they got the first time.
You upgraded your plan. A higher tier gives the router more engines to try. Assets that were previously skipped may now find a result — this is the single most common reason to re-run, and it targets exactly the assets that failed before.
You added a location after the fact. Media that existed in a folder before you started watching it needs a one-off run to be processed.
The upstream source changed. If assets were re-uploaded or replaced in your platform, they're new files as far as Inverity is concerned and will be picked up automatically if they land in a watched location.
When re-running does nothing useful
On assets that already saved well. Re-running the same asset at the same profile on the same plan produces the same decision, and consumes volume again for no benefit.
To "try harder" on a skip. A skip under identical settings will skip again. Change something first — the profile, or the plan.
How to re-run
Run optimization on a folder or collection from the dashboard, the same way you process an existing backlog. Inverity works through the assets in that location and applies your current settings.
Re-running consumes volume again
Every asset processed in a re-run is metered at its source size, exactly like a first run. Re-running a large library is as expensive in volume terms as processing it the first time. Scope re-runs to the folders where the change actually matters. See Volume and usage.
A sensible re-run strategy
- Scope it. Pick the folders where the change matters — usually the highest-traffic content, or the folders with the worst previous results.
- Sample first. Re-run one folder, compare against its previous results, and confirm the change did what you wanted.
- Check the volume cost. Note what that folder consumed and extrapolate before widening.
- Then widen. Work through the remaining folders in batches.
What happens to the previous optimized file
The re-run result replaces the current file in your platform under the same write-back rules as a first run. In a DAM, it lands as a new version of the asset, so your version history shows the progression and your master is still untouched. See How write-back works.
If your site or CDN caches assets, purge the cache after a re-run or you'll keep seeing the previous version. See Delivery and caching.