Skip to main content

Inspection Automation Troubleshooting Guide

This article explains common reasons inspection automations may not trigger and what to review in resident information before contacting Support.

Tanajah Lea avatar
Written by Tanajah Lea
Updated yesterday

If an inspection automation did not trigger as expected, it is usually related to move-in/out timing or missing information. Below are the most common reasons this may occur and what to check before contacting Support.


Common Reasons an Automation May Not Trigger

Inspection automations are time-based and rely on resident information being complete before the daily automation run.

Common reasons an automation may not trigger include:

  • The resident was added or updated after the automation was scheduled to run

  • Required move-in or move-out dates are missing from the resident profile

  • The automation skipped the resident due to timing rules


How Inspection Automations Run

Inspection automations are processed once per day at 10:30 AM CST.

Because automations are time-based:

  • Residents must be added and fully updated before 10:30 AM CST to be included in that day’s automation run

  • Any residents added or updated after 10:30 AM CST will not be included until the next scheduled run

  • Automations do not run retroactively for changes made after the daily processing time

  • If an automation does not run on a unit, the inspection needs to be created manually to avoid delays


What to Check First

1. Review Any Reports or Notifications

If you received a report or notification explaining why the automation did not run, review that message carefully. These reports typically explain why a resident was skipped.

If you’re unsure how to interpret the report, our Support team can help.


2. Confirm When the Resident Was Added or Updated

Automations do not run retroactively.

If a resident was added or updated after the automation’s trigger timing, the inspection will not automatically send for that resident.


3. Verify Move-In and Move-Out Dates Are Added

Make sure the resident profile includes:

  • A move-in date

  • A move-out date (if applicable)

Missing or incomplete dates can prevent an automation from triggering correctly.


4. Check Whether the Issue Is Isolated

Determine whether:

  • The automation failed for one resident only

  • The automation failed for multiple residents

If the issue is isolated to one resident, it is often related to timing or missing data.


What Happens Next?

If everything above looks correct and the automation still has not triggered, our Support team can investigate further.

When contacting Support, please include:

  • The property address

  • The resident's name

  • The automation you expected to trigger

  • Any reports or notifications you received

This information helps us resolve the issue more quickly.

Note: If an inspection was not generated automatically, we recommend manually creating the inspection to ensure it is sent on time

Did this answer your question?