Error when trying to push publish with specific workflow subactions setup
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
Given this workflow action configuration
There's this error returned when trying to execute the workflow action:
ERROR: duplicate key value violates unique constraint "identifier_pkey" Detail: Key (id)=(5347312168dfdad9901ba62079f96852) already exists.{ "SQL": ["INSERT INTO identifier (parent_path,asset_name,host_inode,asset_type,syspublish_date,sysexpire_date,owner,create_date,asset_subtype,id) values (?,?,?,?,?,?,?,?,?,?)"], "maxRows": [-1], "offest": [0], "params": [ "/", "content.81d5b63a-79bb-4062-9058-6dec3c779c17", "24057e9a-4fae-4a97-a9ba-400ef52dce8a", "contentlet", null, null, "dotcms.org.1", "2026-04-02 18:09:21.922", "Donation", "5347312168dfdad9901ba62079f96852" ] }
Steps to Reproduce
Have a Push Publish sender and receiver configured.
Recreate a workflow action like the one shown in the image, including the same actionlets/subactions.
Attempt to execute the workflow action when creating a piece of content of the sender.
After selecting the Push Publish environment and filter and clicking "Send", it will fail with the error stated above.
Acceptance Criteria
The given combination of actionlets under an action needs to work without issues.
dotCMS Version
main / trunk_50c837a
Severity
High - Major functionality broken
Links
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the workflow action with the shown actionlets, using a Push Publish sender and receiver, then inspect the execution path after selecting the environment and filter. Trace the duplicate identifier insertion reported in the error. Done means the same actionlet combination completes successfully when publishing newly created content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100