Users may notice that documents previously deleted in a task reappear later during a Periodic Review or in subsequent tasks within the same journey. This behaviour is expected and is related to how Document Persistence is configured.
Why This Happens
Document persistence works at the task level. This means that:
When a task with document persistence enabled moves to “In Progress”,
all documents that were originally marked to be persisted at the start of the journey are restored.If there are multiple document tasks in the same journey with persistence enabled,
documents removed in an earlier task can reappear in a later task.
In simple terms, the system “remembers” the original set of documents and re-applies them when a new persisted task begins.
Example Scenario
Documents are uploaded at the start of a journey
Task 1 begins (with persistence enabled) → documents are available
A user deletes some documents in Task 1
Task 2 begins (also with persistence enabled)
The previously deleted documents reappear
This happens because persistence re-applies the original document set at each relevant task.
When Document Persistence is NOT Enabled
If document persistence is disabled:
Documents will still move between tasks within the same journey
However, deleted documents will not reappear in later tasks
Documents will not persist across different journeys
Example:
Upload document in Task 1
Delete it in Task 1
Move to Task 2 → the document will not reappear
Key Points
Document persistence is task-driven, not user-action driven
Deleted documents may return if persistence is enabled in later tasks
This is expected system behaviour, not a defect
Behaviour depends on how the journey and tasks are configured
If document persistence is enabled, documents can reappear in later tasks even after being deleted earlier. If it is disabled, deleted documents will remain removed.