Classic UI has never meant to offer full support for Adaptive Forms authoring. The functionality was created for Touch UI

Did you have a chance to clear a browser cache or use an Incognito Tab?

An AEM >=6.4 has a built-in feature for that Bulk Metadata Import and Export In AEM 6.1 I could only thin about a Bulk editor: The Bulk Editor

Did you run your ACS Emai via Approve for Adobe Campaign workflow? It's a mandatory requirement for publishing to ACS process.Your ACS Email in AEM should then include cq:acApproved property and the value is set to true:

You can run a test with a modified OOTB DAM UPDATE ASSET OFFLOADING, you can simply add Activate Page/Asset step:

Just to add to the thread, you can also use a very handy "Dispatcher Flush UI" from ACS Common tools: Dispatcher Flush UI

For AEM 6.5 you can configure "Connected assets" - AEM Assets. & Use assets from a Connected Assets instance in your web pages It allows using centralized DAM between many AEM authors.For an author and publish AEM you can employ a share datastore (S3 for AWS): Configuring node stores and data stores...

You can employ a custom health check:Adobe Experience Manager Help | Building Health Checks for AEM

Try to force clientlibs re-compilation [1] and clear browser's cache[1] How to force a recompilation of all Sling scripts jsps, java, and sightly in AEM 6.4

In theory, you can distribute any type of node via Sling User Synchroimniztaion service. For that you need simply ad a type of a node into "AEM Communities User Sync Listener":You need to keep in mind, that-  Sling User Synchroimniztaion meant to sync between publish instances; the common use case i...