HomeTroubleshooting Hub › Troubleshooting Hub — start here

Troubleshooting Hub — start here

Purpose: Route from symptom to the right diagnostic page, and set the universal first steps.

Who this page is for

AudienceWhy it matters to you
All engineersBookmark for bad days

Universal first three moves

  1. error.log first — tail it while reproducing; most AEM mysteries announce themselves there.
  2. What changed? — deploys, config, content ops, SP installs in the window before the symptom (dashboards + release annotations).
  3. Which layer? — reproduce against publish directly, then dispatcher, then CDN; the first correct layer localises the fault.

Method in full: The triage method.

Symptom router

You seeGo to
Code deployed but not running / bundle InstalledBundle won't start
Component missing, wrong, or raw placeholderComponent not rendering
Dialog won't open / fields missing / values not savingDialog issues
Model null in HTL / fields emptySling Model injection failures
Stale/missing content on the siteDispatcher caching issues
Author changes never reach publishReplication queue blocked
Slow pages, traversal warningsSlow queries & indexes
Disk filling, backups slowingRepository growth
Users can't log in / can't see contentLogin & permissions
Workflows piling up / stuckWorkflow stuck
High CPU / OOM / GC thrashMemory & CPU issues
mvn install fails / package won't installBuild & deploy failures

Quick navigation