[ https://issues.apache.org/jira/browse/SYNCOPE-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950876#comment-17950876 ]
ASF subversion and git services commented on SYNCOPE-1878: ---------------------------------------------------------- Commit 03ed488fe8380c9de0dac3f9e210ab0b9c4627ca in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=03ed488fe8 ] [SYNCOPE-1878] Priority propagation fails only when ExecStatus.FAILURE > 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)