[
https://issues.apache.org/jira/browse/SYNCOPE-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951157#comment-17951157
]
ASF subversion and git services commented on SYNCOPE-1878:
----------------------------------------------------------
Commit bd74b2a3f3f6b5cf13075c26935e9c86eb2f7480 in syncope's branch
refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=bd74b2a3f3 ]
[SYNCOPE-1878] Refactoring PriorityPropagationTaskExecutor
> Priority propagation failing with NOT_ATTEMPTED
> -----------------------------------------------
>
> Key: SYNCOPE-1878
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1878
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.11, 4.0.0-M1
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Fix For: 3.0.12, 4.0.0, 4.1.0
>
>
> As [specified by the reference
> guide|https://syncope.apache.org/docs/reference-guide.html#propagation] the
> default propagation process is halted whenever the first sequential task,
> defined according to the propagation priority value of the target resources,
> fails.
> With SYNCOPE-1692, however, incremental propagation might result into tasks
> executed with result status {{NOT_ATTEMPTED}} because no actual data was set
> for propagation.
> Such cases are currently treated as failures, and are then causing the
> propagation process to halt according to the definition above, which does not
> seem correct.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
