Clear cache and reactivate Omniscript on the browser

 

When updating an Integration Procedure or OmniScript (layout or values), make sure to clear cache and reactivate before testing. Otherwise, changes may not reflect correctly. Cache issues can cause outdated values to appear on the test screens.

When working with Integration Procedures (IP) and OmniScripts, it’s common to make updates to layouts, data mappings, or values and expect immediate results during testing. However, one often overlooked factor can lead to confusion—caching.

🚨 The Issue

After making changes, you may still see old values or layouts during testing. This can make it seem like your updates didn’t apply, even though everything is configured correctly.

✅ The Fix

Always follow these steps after making updates:

1. Clear cache
2. Reactivate the Integration Procedure or OmniScript

💡 Why This Happens

OmniStudio components leverage caching for performance optimization. If not cleared, cached data can continue to serve outdated responses, especially in multi-step flows where previous screens rely on stored values.

🧪 Real-World Insight

I encountered this while testing updates—everything looked correct in configuration, but the UI still showed old data. Clearing the cache and reactivating immediately resolved the issue.