Troubleshoot missing records, uploads and background work
Start with the exact property, record reference, action and error message.
Before you start
Start with the exact property, record reference, action and error message. Separate a permission problem from a validation or background-processing problem.
Follow these steps
- Confirm the intended workspace and active Property & Compliance Management dependency.
- Check Flow and native domain permissions for the affected user.
- Open the source record and verify its active client/property/job relationships.
- For uploads, check the allowed type, actual file content, size and storage availability.
- For delayed work, check cron operation, queue approval, scheduled time, attempts and action logs.
- Reopen the record after an uncertain save before retrying and provide support with the reference and observed state.
Check it worked
You have enough non-secret evidence to identify the failed boundary without creating duplicate business actions.
If something does not look right
Do not treat a success alert, readiness score or completed queue status as proof of every downstream effect. Inspect the stored record, evidence, recipient action or ledger source.
Questions and answers
Which upload limits apply?
Migration and reconciliation CSVs: 5 MB and 5,000 rows. Flow credential evidence: PDF or supported image, maximum 10 MB. Supplier completion uploads follow the native maintenance upload validation.
Why does a direct file link show not found?
Protected file delivery checks authentication, tenant storage path, role and record ownership.
Does deactivation delete evidence?
The module’s lifecycle preserves stored data. Deactivation removes its active hooks and navigation; it is not a data-cleanup operation.