In the ex libris guidance

How to Publish Content - Ex Libris Knowledge Center (exlibrisgroup.com) suggests it would “Most changes you make in campusM will be seen by the end-user if they log out and back in to the app, or switch profiles. You can force these changes to appear immediately by publishing the app.”

However, if you update content in creative studio or content pages and use the publish mechanisms when changed and saved via App Settings >Content > Content then published via App Settings > Publishing > Publish or via edit and Save and Publish in Creative Studio the changes are not reflected in the view seen by end users on the web.

We need a mechanism that either flags updated content as stale so they are retrieved from the web rather than cache or the content is set to expire in cache after 2-3 days at most.

The app will identify the content has been changed and on re-entering that content page will do a refresh for changes, the web though will not see the updates until either doing a forced refresh or log out and login again. This according to dev is as designed, this is a poor UX, a user won't know if content has been refreshed so getting them to refresh on the off chance is a not making the product a compelling experience.
We have remove the connect layer so can set the login lifetime to 90 days meaning if content aimed at students in the busy enrolment season is updated there's a chance it won't be seen until December when they're already getting ready for end of the term.
Dev have also confirmed we cannot use meta tags to set a expiry on the content.

We have heavily utilised content so are particularly affected now we have moved to the 90 days login lifetime from 2 days - this was a particular pain point for our users.