Legal Data Tech
DEPLAW

Automation & AI

Workflow Incidents

If a workflow step gets technically stuck, it becomes its own incident with an error message and case reference – technical staff can intervene in a targeted way instead of running workflows blind.

DEPLAWapp.dep.law
Workflow Incidents2 open
Unreachable BPMN elementOpen
Task_7a3f · Workflow "Dunning run stage 2" · Case INK-2024-1102
Timer event not triggeredOpen
Timer_wv02 · Workflow "Case intake" · Case LIT-2024-0312
Condition could not be resolvedResolved
Gateway_ex1 · Workflow "Dunning run stage 2" · Case INK-2024-0847
Error message
Required field missing: opposing party address · Task_7a3f could not be executed.
For resolution by technical staffMark as Resolved

Workflow incidents are a technical output for developers and technical staff to resolve errors in running workflows in a targeted way. If a single step in a BPMN workflow gets technically stuck — for example because an expected element is unreachable or a condition never resolves — that process doesn’t show up as an inconspicuous background failure, but as its own, clearly named incident.

An error message instead of guesswork

Every incident carries the specific error message required to fix it. Technical staff no longer have to reconstruct the failed process from server logs — they see directly where in the workflow, and in which case, the error occurred.

Resolution documented internally

Once an error is fixed, the incident can be set to the status “Resolved.” This documents internally that — and when — the issue was handled, and keeps the list of open incidents limited to the errors that genuinely still need attention.

01

An error instead of a silent stall

If a step in a running workflow fails — for example an unreachable BPMN element or a timer event that never fires — DEPLAW turns it into its own incident instead of leaving the process sitting unnoticed in the background.

Technical output per error

02

Error message with case reference

Each incident includes the specific error message needed to resolve it — together with the affected workflow and the corresponding case, instead of a generic system error without context.

Directly traceable to the case

03

Can be marked as resolved

Once an error is fixed, technical staff set the incident's status to "Resolved" — the fix is thereby documented internally and the incident disappears from the open list.

Status: Resolved

See this feature live.

Book a free demo