dotCMS / dotCMS/core

Delete workflow with Push/Remove Now + Delete Content — content not removed from higher environment

Open
#34,626 0 comments 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 a Delete workflow action includes both Push/Remove Now (pushRemove=true) and Delete content subactions, the content is deleted from the lower (source) environment but is never removed from the higher (target) environment and remains published there.

This affects any setup using a delete workflow that pushes remove to remote environments and then deletes locally.

Impact: content that should be removed from all environments stays live on higher environments, causing inconsistency and potential compliance/accuracy issues.

Steps to Reproduce
  1. Configure a workflow Delete action with two subactions: Push/Remove Now(with "Push Remove" enabled, targeting the higher environment) and Delete content (order may be either way).
  2. On the lower environment, run the Delete workflow action on a piece of content that is published to the higher environment.
  3. Observe: content is deleted from the lower environment.
  4. Observe: content remains published on the higher environment (not unpublished/deleted).

https://drive.google.com/file/d/16CMxLP0LpU74IYUBtOiF8KxuBIWZey2v/view?usp=sharing

Acceptance Criteria
  • With Push/Remove Now + Delete content in a Delete workflow action, content is removed (unpublished/deleted) on the higher environment when the workflow runs.
  • Behaviour is correct regardless of actionlet order (Push/Remove Now before or after Delete content), or order is documented and enforced so the correct sequence works reliably.
dotCMS Version

latest 26.01.30-01,
26.01.22-02

Severity

Medium - Some functionality impacted

Links

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

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

Start by tracing the Delete workflow entry point and the Push/Remove Now and Delete content subactions described in the reproduction steps. Reproduce the workflow against lower and higher environments with both actionlet orders, then verify that the content is unpublished or deleted on the higher environment regardless of order.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.