Push delivery fails during workflow execution in Adobe Campaign Classic v8
In Adobe Campaign Classic FFDA v8, push delivery fails during workflow execution at the target preparation stage because workflow temporary tables are created in Postgres while delivery preparation runs in Snowflake. In an FFDA deployment, Campaign uses a local Postgres database for some operations and a Snowflake cloud database for campaign execution and workflows, so temporary tables and delivery preparation run on different databases. This mismatch causes Snowflake to reference temporary tables that don’t exist. To fix this, move the audience data to Snowflake before the Delivery activity.
Description description
Environment
- Product: Adobe Campaign Managed Cloud
- Product Version: v8
- Console Build: 8.8.1
- Server Build: 8.8.1
- Production Environment
Issue/Symptoms
- Push deliveries fail during workflow execution at the target preparation or analysis stage.
- Error messages include XSV-350122, SOP-330011, and ODBC errors referencing missing or unauthorized temporary tables.
- Error example: SQL compilation error: Object ‘WKF7430953_21_1_ALL’ does not exist or not authorized. SQLState: 42S02.
- The issue occurs even when targeting a single profile or device and with platform‑specific audiences.
Resolution resolution
To resolve this issue, follow these steps:
- Open your workflow in Adobe Campaign v8.
- Identify where the audience is read into the workflow, such as through a Read Group activity.
- After using any segmentation or sampling step (like Split or Extract), add a Change Data Source activity right before the Delivery activity.
- Configure the Change Data Source activity to move audience data from Postgres to Snowflake.
- Ensure the Delivery activity receives its audience from the Change Data Source output.
- Save and execute the workflow.
- Verify that push delivery completes successfully without temporary table errors.
Note:
This solution ensures that all working tables used by delivery preparation reside on Snowflake, preventing cross-database access issues during push notification workflows in hybrid database environments.
Related reading
- Campaign FFDA deployment in Campaign v8 architecture documentation
- Get started with Campaign architecture in Campaign v8 architecture documentation
- Get started with workflows in Campaign v8 workflow documentation
- Create and send push notifications in Campaign v8 channel configuration documentation
- Get started with push notifications in Campaign Web v8 in Campaign Web v8 channel documentation