Too many workflows are triggered by a workflow launcher configuration set on node

Too many workflows are triggered by a workflow launcher configuration set on node_modified event

Išči

Na tej strani

Velja za: Experience Manager Experience Manager 6.3 Experience Manager 6.4 Experience Manager Dispatcher

某些 Creative Cloud 应用程序、服务和功能在中国不可用。

A custom workflow launcher configuration is firing too many times.

The launcher has Event Type="Node modified" and Condition set with a condition like "property==value".

The launcher is triggering the workflow too many times.

AEM 6.x

The workflow launcher is triggered for any modification to the node where there property value matches the condition criteria.

It doesn't only get fired when the property in the condition itself is modified.

The solution to the problem is to make sure only one event is picked up by the launcher condition.

Here are the possible resolutions

Configure the Exclude List with a comma separated list of properties of the node to ignore modifications for.

This may or may not be enough to avoid the problem (depending on the property the condition is defined for).
Add a custom property to the node then have that property get removed by the workflow step.

Then you can set the condition to listen to the change to that property's value.
Implement a custom JCR event listener instead.

See for example https://helpx.adobe.com/experience-manager/using/maven_arch12_event_listener.html

Too many workflows are triggered by a workflow launcher configuration set on node_modified event