Hi, Users should be accessing app servers using an active/passive load balancer, or just connect directly to the primary.In active/active, users won't be able to reliably unconditionally stop workflows.You should still mount the app servers to a common share for failover. Thanks,-Jon
Hi, Are you copying broadLog into another table?If so, may be simpler to move out of campaigns into its own periodic ETL workflow- Every day, select newly modified rows, update position marker, upsert table. Thanks,-Jon
Hi, AFAIK in-app messaging is not currently supported in ACC.It is in ACS via Launch though:https://docs.adobe.com/content/help/en/campaign-standard/using/communication-channels/in-app-messaging/about-in-app-messaging.html Thanks,-Jon
ACC doesn't tolerate corruption at all in objects, and will gray out the UI when it's detected. AFAIK [view/eventDate] is not an ootb field, so delete and recreate.
Hi, This is by design. Two workarounds:Change your js to read the real query string instead of the pseudo query stringCreate a page or jssp that re-redirects, transforming query string params to pseudo-qs params, then link to that instead Thanks,-Jon