SS and SF dependency not triggering When task is no longer blocked rule trigger.

I found this previous post by @Jan-Rienk from July 2024 and a follow-up from @Emily_Roman in January of this year saying this issue was resolved for SS.

However, I’m currently running into the exact same issue.

Any dependencies I’ve set with SS or SF are not triggering a Rule that uses the “Task is no longer blocked” trigger, but using FS or FF can trigger the Rule without issues.

Is this intentional?
Where even though one task is “blocking” another from being completed, because it’s a Start to X relationship, this doesn’t count as being blocked? If so, then from a UI perspective, there should be nothing stopping you from completing a task with a SS or SF dependency to another task. But it very clearly does block a task from being completed within the current UI.

Example for Discussion:

  • There is Task A, B, C
  • I have a rule to update a task’s custom field called “Progress” to “Started” when a task is no longer blocked.
  • Dependencies:
    • Task A has a FS dependency to Task B
    • Task B has a SS dependency to Task C
  • Workflow:
    • When I complete A, Task B is marked as Started.
    • When I complete B, nothing happens to Task C.

Based on this logic, there is no blocker to Task C because it isn’t blocked by B. Task C starts alongside Task B.
But with that same logic, that means Task A is actually the blocker for C because Task C cannot start without Task B which is blocked by Task A.
This appears to mean the Dependencies are non-linear, in the sense that even though A is Blocking B and B is Blocking C, C isn’t actually blocked.

To add a little bit more to the confusion, if I intentionally redate Task C to come on the SAME DAY as Task B and go to the timeline view. The dependency visualization clearly shows that Task C is still being blocked by Task B, even though the relationship is SS and they’re both Starting on the same day.

1 Like

A post was merged into an existing topic: Start to Start dependency doesn’t trigger When task is no longer blocked rule trigger