๐Ÿ› UAT: Location UPDATE bypasses approval workflow - changes committed immediately

Resolved ๐Ÿ’ฌ 1 comment Opened Feb 4, 2026 by raelactao-adi Closed Feb 4, 2026

๐Ÿ› UAT FINDINGS

Tester: Rae
Date: 02/04/2026
Screen: Locations / Workflow Designer
Test ID: Set up for Event 2

---

What I did

Edited an ACTIVE record in locations, which is up for approval.

What happened

Went to Workflow Designer and edited Locations Approval Workflow and Locations Simple Workflow (connected nodes and ensured assigned ROLES Ops Supervisor then Ops Manager is selected). Received a toast message notifying needing approval of Ops Supervisor and Ops Manager except update/edit change is committed right away and displays in audit log / history.

What I expected

Updating an ACTIVE record will proceed through approval workflow before committing changes.

---

Severity

  • [ ] Blocker
  • [x] Major
  • [ ] Minor

---

Technical Notes

  • Location: app/routes/api.location.tsx (PUT handler)
  • Expected behavior: UPDATE operation should create ApprovalInstance with operation: UPDATE, store before_data and after_data, and NOT apply changes until workflow is approved
  • Actual behavior: Changes appear to be applied immediately to the database despite workflow being configured

Related Files

  • app/routes/api.location.tsx
  • app/utils/approval-chain.server.ts
  • app/routes/locations.tsx

View original on GitHub โ†—

This issue has 1 comment on GitHub. Read the full discussion on GitHub โ†—