workflow-launchers

To auto-start workflows on JCR content changes in AEM 6.5, configure a cq:WorkflowLauncher under /conf/global/settings/workflow/launcher/config. Point its workflow property to a runtime model under /var/workflow/models to trigger automated execution on matching events.

AEM workflow launcher configurations require properties including eventType, glob, nodetype, workflow, enabled, and runModes. These properties define the JCR event triggers, target paths, workflow model references, and deployment restrictions for the launcher.

Yes, you can restrict workflow launchers to specific AEM run modes using the runModes property. This ensures automated workflows only trigger in designated environments, such as author or publish instances, preventing unintended executions.

You can overlay out-of-the-box AEM workflow launchers by configuring custom launcher nodes that override OOTB behavior while preserving core system integrity. This approach allows you to modify triggers for asset uploads or content edits without altering baseline system files.

If your AEM workflow launcher is not triggering, verify the eventType, glob pattern, and nodetype properties match your JCR changes. Debugging guidance suggests checking if the launcher is enabled and confirming the workflow path points to a valid runtime model.

Use workflow launchers when you need to automatically start workflows in response to JCR content changes, such as triggering processes on asset uploads or content edits under specific paths. Manual workflow starting is less efficient for repetitive content-driven automation tasks.