You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2025/05/12 09:08:00 UTC
[jira] [Resolved] (SYNCOPE-1878) Priority propagation failing with NOT_ATTEMPTED
[ https://issues.apache.org/jira/browse/SYNCOPE-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-1878.
---------------------------------------------
Resolution: Fixed
> 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)