What is causing a timeout during Functional Testing due to distribution queues being blocked on content package?

What is causing a timeout during Functional Testing due to distribution queues being blocked on content package?

• A. The sling-distribution-importer user has insufficient permissions in the Publish Service.
• B. The sling-distribution user has insufficient permissions in the dev environment.
• C. The sling-distribution user has insufficient permissions in the Author Service.
• D. The distribution queues are blocked due to a network outage.

Answer: (A)

Distributions in AEM rely on a dedicated system user, sling-distribution-importer, to push content from the author to the publish instance. The publish service must grant this user the right permissions to receive, write, and apply the distribution package on the publish side. When these permissions are insufficient, the publish side cannot process the incoming package, so the distribution queue stalls and the functional test times out waiting for the queue to complete. The other options don’t fit as neatly: permissions issues in the dev environment or in the Author Service would block operations on those specific environments, not the publish-side processing of the distribution, and a network outage would typically show connectivity problems rather than a clean permission denial in the publish flow.

Distributions in AEM rely on a dedicated system user, sling-distribution-importer, to push content from the author to the publish instance. The publish service must grant this user the right permissions to receive, write, and apply the distribution package on the publish side. When these permissions are insufficient, the publish side cannot process the incoming package, so the distribution queue stalls and the functional test times out waiting for the queue to complete. The other options don’t fit as neatly: permissions issues in the dev environment or in the Author Service would block operations on those specific environments, not the publish-side processing of the distribution, and a network outage would typically show connectivity problems rather than a clean permission denial in the publish flow.