A customer reports that the campaign workflows are not running. When restarting or starting workflows the status changes to as Start/Restart requested and the Start. Pause buttons are disabled.
The Architect notices that all process are running as expected in the Monitoring Tab.
What is causing the issue?
This issue occurs when the wfserver process is not set to automatically start when the server is restarted. This means that the workflows will not run unless the wfserver process is manually started. The Start/Restart button will be disabled and the process will not run until it is manually started.
A customer is migrating its legacy marketing platform with Adobe Campaign.
The customer has dependencies on a few significant custom database functions that enabled specific string manipulations and custom encryption.
While developing workflow, the team struggle to match these functions that the customer was able to use prior to Adobe Campaign.
What should the Architect recommend?
This allows the customer to continue using their custom functions within the Adobe Campaign platform. This option allows the customer to keep using their custom functions within the Adobe Campaign platform and also allows the team to use these functions directly in the workflows.
Top of Form
Bottom of Form
A customer has a data retention policy for the logs in Adobe Campaign Classic of 365 days. They send over 1 million emails per month.
The Architect designs a workflow with a scheduler that triggers every 10 minutes querying the recipient delivery log. What is the risk with this workflow?
The customer's data retention policy for the logs in Adobe Campaign Classic of 365 days means that the workflow should retrieve records for the past 365 days in order to keep the data retention policy. However, the workflow is designed to trigger every 10 minutes, meaning that it will only query a small portion of the log data per iteration. This could result in the workflow not retrieving all of the expected records due to the limited time.
Top of Form
A customer is migrating its legacy marketing platform with Adobe Campaign.
The customer has dependencies on a few significant custom database functions that enabled specific string manipulations and custom encryption.
While developing workflow, the team struggle to match these functions that the customer was able to use prior to Adobe Campaign.
What should the Architect recommend?
This allows the customer to continue using their custom functions within the Adobe Campaign platform. This option allows the customer to keep using their custom functions within the Adobe Campaign platform and also allows the team to use these functions directly in the workflows.
Top of Form
Bottom of Form
A customer reports that the campaign workflows are not running. When restarting or starting workflows the status changes to as Start/Restart requested and the Start. Pause buttons are disabled.
The Architect notices that all process are running as expected in the Monitoring Tab.
What is causing the issue?
This issue occurs when the wfserver process is not set to automatically start when the server is restarted. This means that the workflows will not run unless the wfserver process is manually started. The Start/Restart button will be disabled and the process will not run until it is manually started.
Sherita
6 months ago