Configure workflow settings workflow-settings
When creating a workflow or orchestrating workflow activities in the canvas, you can access advanced settings related to the workflow. For example, you can set a specific timezone for the workflow, manage how the workflow should behave in case of error, or manage the delay after which the workflow history should be purged.
These settings are pre-configured in the template selected when creating the workflow, but can be edited as needed for this specific workflow.
Workflow properties properties
The Properties section provides generic settings which can be configured when creating a workflow. To access the properties of an existing workflow, click the Settings button available in the actions bar above the workflow canvas.
These properties are:
-
The Label of the workflow that displays in the list.
-
The Internal name of the workflow.
-
The Folder where the workflow should be saved.
-
The default Timezone to use in all the workflow’s activities. By default, the workflow’s time zone is the one defined for the current Campaign operator.
Possible values are:- Server time zone to use the time zone of the Adobe Campaign application server
- Operator time zone to uses the time zone of the Adobe Campaign operator who executes the workflow, as defined in the operator’s profile, in the client console
- Time zone of the database to use the time zone of the database server
- A specific time zone
-
When a workflow fails, the operators belonging to the operators group selected in the Supervisor(s) field are notified by email.
-
You can also enter a Description of your workflow.
When the workflow is associated to a campaign, it is displayed in the Linked campaign field. You can open the associated campaign from that field.
Segmentation settings segmentation-settings
-
Targeting dimension: Select the targeting dimension to use to target profiles: recipients, contract beneficiaries, operator, subscribers, etc. Learn more about targeting dimensions
-
Keep the result of interim populations between two executions: By default, only the working tables of the last execution of the workflow are kept. Working tables from previous executions are purged by a technical workflow, which runs on a daily basis.
If this option is enabled, working tables will be kept even after the workflow has been executed. You can use it for testing purposes and hence must be used only on development or staging environments. It must never be checked in a production workflow.
Execution settings exec-settings
-
History in days: Specifies the number of days after which the history must be purged. The history contains elements related to the workflow: logs, tasks, events (technical objects linked to the workflow operation). Default value is 30 days for out-of-the-box workflow templates. Purge of the history is performed by the Database cleanup technical workflow, which is executed by default everyday
note important IMPORTANT If the History in days field is left blank, its value will be considered as “1”, meaning that the history will purged after 1 day. -
Default affinity: If your installation includes several workflow servers, use this field to specify the server which the workflow will be executed on. This forces the execution of that workflow on a particular server. You can choose any existing affinity name, but make sure you do not use spaces or punctuation marks. If you use different servers, specify different names, separated by commas.
note important IMPORTANT If the value defined in this field does not exist on any server, the workflow will remain pending. -
Save SQL queries in log: Check this option to you to save the SQL queries from the workflow into the logs. This functionality is reserved for advanced users. It applies to workflows that contain targeting activities like Build audience. When this option is enabled, the SQL queries sent to the database during workflow execution are displayed in the workflow’s logs, allowing you to analyze them to optimize queries or diagnose issues.
Error management settings error-settings
-
Error management: This field lets you define the actions to be taken if a workflow task has errors. There are three possible options:
- Suspend the process: The workflow is automatically paused and its status changes to Failed. Once the issue is solved, resume the workflow using the Resume buttons.
- Ignore: The status of the task that triggered the error changes to Failed, but the workflow keeps the Started status.
- Abord the process: The workflow is automically stopped and its status changes to Failed. Once the issue is solved, restart the workflow using the Start buttons.
-
Consecutive errors: This field becomes available when the Ignore value is selected in the In case of errors field. You can specify the number of errors that can be ignored before the process is stopped. Once this number is reached, the workflow status changes to Failed. If the value of this field is 0, the workflow will never be stopped regardless of the number of errors.
Initialization script initialization-script
The Initialization script lets you initialize variables or modify activity properties. Click the Edit code button and type the snippet of code to execute. The script is called when the workflow executes. Refer to the section related to event variables.