Skip to main content

Error: 'ORA-02290 check constraint (FW.WORKFLOW_STATUS_ASSI_134074783) violated'

In this article, we explain how closing a step can fail due to a check constraint violation during a database update.

Y
Written by Yusef Abulaynain
Updated over 5 months ago

Error:
'### The error may involve mosaic.sensitive.step.updateNextAction-Inline
### The error occurred while setting parameters
### SQL: UPDATE mo_workflow_steps SET workflow_step_priority = ?, completed_on = ?, incoming_on = ?, delayed_incoming_datetime = ?, assignment_note = ?, started_on = ?, assignee_id = ?, assignment_datetime = ?, is_terminator = ?, subgroup_id = ?, responsible_team_id = ?, last_updated_by_worker_id = ?, last_updated_for_worker_id = ?, last_updated_on = getdate() WHERE workflow_step_id = ?
### Cause: java.sql.SQLIntegrityConstraintViolationException: ORA-02290: check constraint (FW.WORKFLOW_STATUS_ASSI_134074783) violated'

This log error can happen when one of the next actions from the step doesn't have a responsible team. Check the step and see if any details are missing from the selected next actions.


​

Did this answer your question?