/hoa-software-setup-guides/

AppFolio Property Manager: Violation Status Not Updating After Resolution

Fix AppFolio violation status not updating after resolution: common causes, correct settings, workflow checks, and troubleshooting steps.

Schedule Demo

Reviewed by:

D. Goren

Head of Content

Updated Dec, 6

More Than Just Rules. A Community That Cares.

A single platform where homeowners submit requests, boards review them, and everyone sees the status without confusion or back-and-forth.

Schedule Demo

AppFolio Property Manager: Violation Status Not Updating After Resolution

A violation status in AppFolio usually doesn’t update after “resolution” because the item was only noted in a comment or task, but the violation record itself was never moved to a Closed/Resolved status, the next inspection step wasn’t completed, or an automation/workflow is holding it in the prior state. Even if everything looks correct, the status may be blocked by permissions, a required field, or a sync delay.

 

 Most common causes (and what they mean) 

  • Resolved in notes, not in the violation: Adding a note like “fixed” doesn’t change the status. The status only changes when the violation’s Status field is updated.
  • Wrong screen updated: Updating a work order, task, or inspection does not automatically close the violation unless your setup links them.
  • Violation requires a follow-up inspection: Some setups keep it “Open” until a re-inspection result is recorded (pass/fail).
  • Required fields missing: AppFolio may not save the status change if a required field (resolution date, resolution code, inspector, etc.) is blank.
  • Permissions: The user can view/edit notes but cannot change Status (role restriction).
  • Automation rules overriding: A rule may reopen it (example: “If not compliant by date, set to Escalated”).
  • Cached view/report filter: The violation is closed, but the list is filtered to show “Open,” or the page hasn’t refreshed.

 

 Step-by-step fix (works even if everything “should” be correct) 

  • Open the specific violation record (not just the unit/owner page). Look for a section labeled Status, Outcome, or Violation details.
  • Change Status to Resolved/Closed and enter any required fields (commonly Resolution date and Resolution notes).
  • If there is a Re-inspection or Follow-up area, record the result as Compliant (this is what actually triggers closure in some configurations).
  • Click Save, then fully refresh the page. Re-open the violation to confirm the status persisted.
  • Check the violations list filters: set to All or include Closed to confirm it moved.

 

 Troubleshooting when it still won’t change 

  • Status snaps back: Look for an automation/escalation rule tied to due dates. Temporarily adjust the rule or update the compliance date so it stops re-triggering.
  • No option to close: That’s usually permissions or a configuration that only allows closure through an inspection outcome. Test by using an admin role or completing the inspection step.
  • Saved but reports still show open: Reports often use a snapshot date or filters. Re-run with updated date range and include closed statuses.
  • Multiple violations for the same issue: The “open” one might be a different record. Sort by created date and confirm the correct ID is closed.

 

 When to contact AppFolio support 

  • Status field missing or cannot be edited even with admin access
  • Automation rules are unclear or managed at a higher account level
  • Violations appear closed in the record but API/export/report still shows open after refresh and re-run

Because your community deserves clarity

Structured workflows for ARC requests, violations, appeals, and documents — so every decision follows the same transparent steps.

Quick Checks for Violation Status Not Updating After Resolution (AppFolio)

Confirm the Violation Was Actually Closed

Check that the violation record is marked as resolved/closed (not just noted in comments) and that a resolution date or final action was saved.

Check for Required Fields Blocking Status Changes

Verify any required resolution fields (resolution type, compliance date, fine outcome, assigned user) are completed—missing fields can prevent the status from updating.

Look for Pending Approvals or Workflow Steps

Some setups require manager/board approval or a follow-up task before the system updates the status. Review any pending tasks, approvals, or review queues tied to the violation.

Refresh, Permissions, and Sync Delays

Try a hard refresh and confirm your user role can edit violations. If integrated with inspections or portals, allow time for sync or check for integration errors that delay updates.

Ready to experience a faster, smarter, and fairer way to manage your community? Schedule Demo.

No more chasing signatures, emails, or approvals

Automate reminders, deadlines, notices, and follow-ups — reducing manual admin so your board can focus on real community issues.

Leanr More About AppFolio Property Manager

AppFolio Property Manager for HOAs Review: Features, Uses, Comparisons

Discover AppFolio Property Manager for HOAs with key features, pros, cons, and top comparisons to find the best fit for community management