frappe-core-workflow

Frappe workflow documents get stuck during state transitions due to invalid docstatus changes or permission errors. Configure forward-only state paths like Draft→Submitted→Cancelled and apply transitions via the workflow engine rather than manually calling doc.submit() or doc.cancel().

Conditional workflow transitions in Frappe use safe_eval-compatible Python expressions applied to document fields. Configure the condition expression on the transition so actions appear only when specific document thresholds or field values are met.

Prevent Frappe workflow permission errors by assigning the correct allowed roles to each transition. Ensure the workflow configuration specifies exactly which roles can trigger state changes so the system validates user permissions correctly.

You can control self-approval in Frappe workflows using the allow_self_approval setting. Configure this parameter within the workflow engine to explicitly permit or restrict the document creator from triggering their own approval transitions.

Valid docstatus transition rules for Frappe workflows require forward-only state paths: Draft (0) to Submitted (1) to Cancelled (2). The workflow engine enforces these rules to prevent illegal 0 to 2 transitions or backwards state movements.

A correct Frappe Workflow DocType schema requires defined states, transitions, allowed roles, and doc_status values. You need this schema to properly structure the workflow engine so documents move reliably between states without permission failures.