Manage Purge

Perform, monitor, and verify purge operations directly from the Medianova Control Panel to ensure updated or corrected content is instantly served to your users.

You can manage Purge operations in the Medianova Control Panel or via API.

Log in to the Medianova Control Panel, select a CDN Resource in the CDN section, and navigate to the Purge tab.

Purge Cached Files

Purge instantly removes cached files from all Medianova edge locations. This is useful when your updated content is not yet reflected or when you want to remove outdated assets.

1

Enter File Path

In the Path field, type the exact file or directory path you want to purge. You can specify multiple paths by entering one per line.

Example:

/myimages/subfolder/image.png
/assets/css/*

2

Use Wildcards

You can use the * symbol to purge multiple files within a directory.

Examples:

• /images/* — removes all files and subdirectories inside /images/

• /images/im* — removes files starting with “im”

• Wildcard purge requires enabling the Wildcard Purge Suffix option in Purge Settings

3

Execute the Purge

Click Purge Files to send the purge request. The system will propagate the request to all CDN nodes and clear the cached content. Purge completion may take several seconds depending on global cache size.

View Purge Logs

All recent purge operations are listed in the Purge Log table below. Use this view to track the status of your requests.

Column	Description
Status	Shows whether the purge is Running, Successful, or Failed.
Task ID	A unique identifier for each purge operation.
File Type	Type of purge — Single, Wildcard, or Full Resource.
Created At	Time the purge was initiated.
URLs	Number of URLs affected.
Running / Successful / Failed	Summary of the operation result.

Click the refresh icon to reload the log and check the latest results.

Troubleshooting

Issue	Description	Recommended Action
Purge failed	Path syntax incorrect or file does not exist.	Verify path and retry.
Wildcard not working	Wildcard purge disabled.	Enable in Purge Settings.
Slow purge completion	Global cache propagation still in progress.	Wait 1–2 minutes and refresh log.
Partial success	Some nodes may have timed out.	Retry failed paths only.

Avoid frequent wildcard purges during peak traffic hours to reduce origin load.