dotCMS / dotCMS/core

[DEFECT] Push Publish Results Missing for Multiple Endpoints

Open
#34,434 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Customer Support Team : Maintenance
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem Statement

When performing push publish to multiple endpoints in an environment configured with "Push to All Endpoints", the results for some endpoints (especially successful ones) are not displayed in the push publish audit details, even though the publish operation completed successfully.

Steps to Reproduce
  1. Configure a publishing environment with "Push to All Endpoints" enabled
  2. Add multiple endpoints to the environment (e.g., one HTTP/DELIVERY endpoint and one S3 endpoint)
  3. Perform a push publish operation to this environment
  4. View the push publish results/audit details
Image Image
Acceptance Criteria

All configured endpoints should appear in the results dialog/audit details with their respective statuses:

  • Endpoint 1 (e.g., DELIVERY) - Status: Success/Publishing
  • Endpoint 2 (e.g., S3) - Status: Success/Publishing
dotCMS Version

Latest, evergreen

Severity

Medium - Some functionality impacted

Links

https://dotcms.freshdesk.com/a/tickets/35120

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the issue with a "Push to All Endpoints" environment containing HTTP/DELIVERY and S3 endpoints, then trace how push publish results reach the results dialog and audit details. Done means every configured endpoint appears with its respective Success or Publishing status.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, content
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.