Patrick Niebeling 9e1a15bab0 Refuse workflows that move cards in a loop ...

Every enabled workflow is an edge "source stack -> target stack";
LoopDetector finds circles in that graph, a workflow whose source is its
own target being the shortest. Without a check, two workflows A -> B and
B -> A move the same cards back and forth on every run, even within a
single run, with a notice for each move. The trigger date is ignored on
purpose: by start date one way and by due date the other, a card with
both dates passed still circles. Chains stay allowed.

The controller rejects saving an enabled workflow that would close a loop
and names the workflows involved. Workflows stored before this check are
skipped by the runner (logged, not disabled) and flagged in the settings
list via a new `loop` field from index().

2026-10-01 13:47:32 +02:00

..

DeckIntegrationService.php

Let workflows move cards by start date instead of due date

2026-10-01 13:19:32 +02:00

DeckUnavailableException.php

Add Deck workflow automation Nextcloud app

2026-08-13 10:13:05 +02:00

LoopDetector.php

Refuse workflows that move cards in a loop

2026-10-01 13:47:32 +02:00

NotificationMailer.php

Let workflows move cards by start date instead of due date

2026-10-01 13:19:32 +02:00

NotificationPolicy.php

Let workflows move cards by start date instead of due date

2026-10-01 13:19:32 +02:00

NotificationPusher.php

Let workflows move cards by start date instead of due date

2026-10-01 13:19:32 +02:00

TriggerDate.php

Let workflows move cards by start date instead of due date

2026-10-01 13:19:32 +02:00

WorkflowRunner.php

Refuse workflows that move cards in a loop

2026-10-01 13:47:32 +02:00