Pages across your website(s) appear to revert to older/outdated versions over time
If content across your website is showing information from previous versions of your pages, the most likely cause is a test or development instance of Cascade CMS running somewhere in your environment.
In order to have somewhat fresh content available for testing/development, many organizations will clone their production database and use that clone for testing. Doing so creates an exact replica of the data in production which includes the connection information stored for publishing to your lives website(s). Because of this, any scheduled publish jobs stored in the database will attempt to fire from the test instance as well.
For any test/development databases cloned from production, we recommend running the database queries mentioned in Setting up a Test Server to ensure that the cloned environment doesn't interfere with your live web site(s).
Once your Destinations are disabled in the test environment, you can manually enable and/or modify your Transports and Destinations to point to test resources as needed.
Publishing a page seems to publish an older version of that page
If publishing an individual page results in no changes to your website, there are a number of potential reasons for that which are outlined in this article.
Assuming that none of those scenarios are occurring - or, when you publish, you actually see older content published to your website as a result - you may be experiencing problems caused by multiple instances of the application running against your database.
In the event that two (or more) instances of Cascade CMS are connected to a single database unintentionally (not in a properly configured load balancing environment, for example), any of those instances of the application can and will publish any job triggered by any other node.
In these cases, since the instances of the application are not synced as they would be in a proper load balanced environment, the node that publishes a job will publish the asset as it appears in its local memory (which can be outdated).
To correct this, make sure you don't have any application environments (which are separate from production) connecting to the production database.