Skip to main content

Clearing Cache

Step-by-step guide to clearing cache for your environments.

Automatic Cache Clearing​

Good news: Urumi automatically clears cache when you deploy changes to Development, QA, or Production. In most cases, you won't need to manually clear cache.

Manual cache clearing is only needed when:

  • Changes aren't appearing after deployment
  • You're using a custom CDN that needs separate clearing
  • You made changes outside the normal deployment flow

From Cache Settings Page​

  1. Navigate to Settings > Cache
  2. Find the environment you want to clear:
    • QA - For testing environment
    • Production - For live site
  3. Click Clear Cache
  4. Wait for the operation to complete

A success message appears when the cache is cleared.

From Deploy Tab​

For quick access while managing deployments:

  1. Go to the Deploy tab
  2. Find the environment card (QA or Production)
  3. Click the archive icon in the card header
  4. Wait for the cache to clear

Environment-Specific Clearing​

Development Environment​

  • Caching is disabled by default
  • No cache clear button is available
  • Changes appear immediately when you refresh

QA Environment​

  • Click Clear Cache on the QA row or card
  • Clears both Nginx and Cloudflare cache
  • Use after pushing changes from Development (if automatic clearing didn't work)

Production Environment​

  • Click Clear Cache on the Production row or card
  • Clears both Nginx and Cloudflare cache
  • Use after pushing changes from QA (if automatic clearing didn't work)

Custom CDN Users​

If you're using your own CDN (like a separate Cloudflare account, Fastly, or another provider):

  1. Urumi clears its own cache automatically during deployment
  2. You must clear your CDN's cache separately
  3. Check your CDN provider's documentation for cache purging instructions

Common CDN cache clearing:

  • Cloudflare - Dashboard > Caching > Configuration > Purge Everything
  • Fastly - Dashboard > Purge > Purge All
  • AWS CloudFront - Create invalidation for /*

What Happens When You Clear Cache​

  1. Request sent - Cache clear request is sent to the server
  2. Nginx purged - Server-side cache is cleared
  3. Cloudflare purged - Urumi CDN cache is cleared globally
  4. Confirmation - Success message appears

The process typically takes a few seconds.

After Clearing Cache​

After clearing cache:

  1. Hard refresh your browser - Ctrl/Cmd + Shift + R
  2. Test the page - Verify your changes are visible
  3. Check multiple pages - Important content should be updated
Propagation Time

CDN cache clearing propagates globally within 30 seconds. If you still see old content, wait a moment and try again.

Best Practices​

Trust Automatic Clearing​

For most users, the automatic cache clearing during deployments handles everything. Only manually clear if you're experiencing issues.

Custom CDN Workflow​

If using a custom CDN:

  1. Deploy changes through Urumi (clears Urumi cache automatically)
  2. Clear your custom CDN cache separately
  3. Verify changes are visible

During Troubleshooting​

If something looks wrong:

  1. Clear cache first
  2. Hard refresh your browser
  3. Test in incognito/private mode
  4. Check on different devices
  5. If using custom CDN, clear that too

Troubleshooting​

Changes Still Not Appearing​

  1. Clear browser cache - Your browser may have its own cache
  2. Try incognito mode - Rules out local caching
  3. Wait 30 seconds - CDN propagation may need time
  4. Check the right environment - Ensure you're viewing the correct URL
  5. Clear custom CDN - If you have one configured

Cache Clear Button Not Working​

  1. Check your connection - Ensure you're online
  2. Refresh the page - Try again
  3. Contact support - If the issue persists