Aem Workflow

adobe/skills/plugins/aem/6.5-lts/skills/aem-workflow

by adobe940b8795c0dfApache-2.0197 starsListed Oct 9, 2026Updated Oct 8, 2026Repository updated today

Single entry point for all AEM 6.5 LTS Workflow skills. Covers workflow model design, custom process step and participant chooser development, launcher configuration, workflow triggering, and production support including debugging stuck/failed workflows, triaging incidents with JMX, Splunk, direct log access, thread pool analysis, and Sling Job diagnostics for the Granite Workflow Engine.

Instructions onlyDevOps & Cloud
AI-generated overview

Routes AEM 6.5 LTS workflow requests to specialist skills covering model design, development, triggering, launchers, debugging and triage.

What it does
This is a single entry point for AEM 6.5 LTS Workflow skills. It presents an intent router table that maps user requests to specialist skills for workflow model design, custom process step and participant chooser development, workflow triggering, launcher configuration, debugging, and incident triage. It also lists 6.5 LTS capabilities and guardrails, such as JMX operations, log access, model paths, and service user guidance. The deliverable is routing guidance that points to the relevant specialist SKILL.md and its output contract.
When to use it
Use this when a request concerns AEM 6.5 LTS workflows and you need to identify which specialist skill applies. It suits broad or ambiguous workflow requests that span multiple concerns, such as design, triggering, launchers, or production debugging. It is also useful for checking 6.5 LTS capabilities and guardrails before acting.
Requirements
Requires AEM 6.5 LTS or Adobe Managed Services (AMS) and a Maven project structure with core and ui.apps modules. It is instructions only and ships no scripts. Referenced specialist skills are expected to be available at the linked paths.

AEM 6.5 LTS Workflow

Route user requests to the appropriate specialist skill based on intent.

Intent Router

User IntentSkillPath
Create a workflow model, add steps, design OR/AND splits, configure variablesModel Designworkflow-model-design/SKILL.md
Implement a custom WorkflowProcess step, ParticipantStepChooser, OSGi service registrationDevelopmentworkflow-development/SKILL.md
Start a workflow from code, HTTP API, Timeline UI, Manage Publication, replication triggersTriggeringworkflow-triggering/SKILL.md
Configure a launcher, auto-start on asset upload, overlay OOTB launcherLaunchersworkflow-launchers/SKILL.md
Workflow stuck, failed step, missing Inbox task, stale instances, thread pool exhaustion, purgeDebuggingworkflow-debugging/SKILL.md
Classify a workflow incident, determine required logs, JMX diagnostics, Splunk queriesTriagingworkflow-triaging/SKILL.md
End-to-end lifecycle or requests spanning multiple concernsOrchestratorworkflow-orchestrator/SKILL.md

How to Use

  1. Match the user's request to one row in the Intent Router table above.
  2. Read the linked SKILL.md for that specialist skill.
  3. Follow the workflow, references, and output contract defined in that skill.
  4. For broad or ambiguous requests that span multiple concerns, use the Orchestrator which coordinates across all specialist skills and loads foundation references.

6.5 LTS / AMS Capabilities

CapabilityDetail
JMXFull access via Felix Console (/system/console/jmx) or JMX client
Retry failed itemsJMX retryFailedWorkItems or Inbox Retry
Stale detectionJMX countStaleWorkflows
Stale restartJMX restartStaleWorkflows(dryRun=true) then execute
PurgeJMX purgeCompleted(dryRun=true) or Purge Scheduler
Log accessDirect filesystem (crx-quickstart/logs/) or AMS log access
Config changesFelix Console, OSGi config in repo, or CRX/DE

6.5 LTS Guardrails

RuleDetail
Avoid editing /libsUse overlays under /apps or store at /conf/global
Model design-time path/conf/global/settings/workflow/models/<id> (preferred) or /etc/workflow/models/<id> (legacy)
Model runtime path (for API calls)/var/workflow/models/<id>
Launcher config paths/conf/global/settings/workflow/launcher/config/ (preferred)
Service usersUse ResourceResolverFactory.getServiceResourceResolver() with a sub-service; avoid loginAdministrative
OSGi annotationsDS R6 preferred; Felix SCR still supported on 6.5 LTS
Deploy viaPackage Manager, Maven + Content Package Plugin

Specialist Skills

  • workflow-model-design/SKILL.md — model structure, step types, variables, and model XML
  • workflow-development/SKILL.md — WorkflowProcess, ParticipantStepChooser, metadata, and error handling
  • workflow-triggering/SKILL.md — Timeline UI, Manage Publication, WorkflowSession API, HTTP API, and replication triggers
  • workflow-launchers/SKILL.md — launcher configuration, JCR event binding, and OOTB overlay
  • workflow-debugging/SKILL.md — stuck workflows, failed steps, JMX remediation, thread pools, and purge
  • workflow-triaging/SKILL.md — symptom classification, JMX diagnostics, log patterns, Splunk queries, and data gathering
  • workflow-orchestrator/SKILL.md — full lifecycle orchestration across all skills

Source and attribution

Source:adobe/skillsinplugins/aem/6.5-lts/skills/aem-workflowat commit940b879

License: Apache-2.0

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal