When the Beacon plan is about to be imported, it locks the edition, the pages and the ads layers. The import does not lock or change the editorial layers of the edition. Therefore, the articles on the editorial layers will still be there after ads reimport.

The import will fail if any user has the edition, pages or ad layers checked out. The Back4 log will tell you if something is checked out and made the import fail.

The Back4 log shows if the plan import has failed, if so then the plan file needs to be moved back into the import folder, or resent.

Example of the page 26 with old plan and a sample article:

The page remained open and only the editorial layer was checked out.

The following screenshot was taken just after the new ad showed up so the ads layer is checked out by the import process, as it was still running.

Therefore, reimporting the Beacon plan will fail if the APM is running as its checks out the edition and pages. Also the APM will fail to start if the plan import is running.

Articles are left on the page and not changed by the plan import, The issue can occur if the new plan removes some pages would removed, but in that case you need to rerun the APM anyway.

See also

About APM and multi-using