An OmniStudio Developer uses an Integration Procedure that is cached. The developer needs to test a feature with fresh, uncached data without affecting the production cache for other users.
Which action should the developer take during testing?
A.
Pass a unique, throwaway value in a non-cache-key input parameter.
B.
Set the Integration Procedure ' s Cache Duration to 0 seconds and republish.
C.
Change the Integration Procedure ' s Type/SubType.
D.
Temporarily disable the Cache property and revert the change after testing.
The best available answer is A, but the wording is not perfect. The safe testing pattern is to avoid changing the published cache configuration used by production users. Changing Cache Duration to 0 or disabling the Cache property would alter runtime behavior for everyone using that active Integration Procedure. Changing Type/SubType is also a bad workaround because it changes the component identity and can break callers. A throwaway test input is the least disruptive option because it lets the developer create an isolated request path for testing rather than clearing or disabling shared production cache. In a real implementation, the test value must affect the effective cache signature; if an explicit Cache Key Property is configured and the throwaway value is outside that key, it will not bypass the cached entry.
================
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit