If content on your live web site is showing old/outdated information, the most likely cause is a test or development instance of Cascade CMS running 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 web site(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.

Did this answer your question?