Where to start
Admin Area → Property Management Flow → Zero-Chase → Execution audit log
Before you begin
Use the execution log to distinguish a processed queue item from a delivered message or created task.
Follow these steps
- Find the queue item and note its entity, property and attempts.
- Read each action status, recipient and message in Execution audit log.
- For email, check the linked client and its active contact; the sender chooses an active contact, preferring the primary one.
- Check workspace mail configuration and the original native record before attempting further processing.
- For exceptions, review last error and retry state; processing retries an exception after about one hour until the attempt limit.
- Check for duplicate effects before re-running work that partly succeeded.
Check the result
You know which action succeeded, which did not deliver, and which source identity it used.
If something does not look right
The tenant-email action first uses the candidate recipient when one is supplied. For a compliance candidate that identity can be the landlord. Do not enable cross-role email actions merely because the action label sounds appropriate; use a verified trigger/recipient combination or staff-only actions.
Questions and answers
Who receives Notify staff?
The current implementation targets up to ten active administrator staff accounts; it is not a configurable assignee list.
Will not_delivered automatically retry?
Not necessarily. A false action result is logged as not_delivered without throwing; the queue may complete. Exception-based failures use the retry cycle.
What does a stale lock mean?
A processing item older than 30 minutes can be returned to pending by the next processing cycle. Review prior effects before further action.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Build and preview a Zero-Chase rule
- Choose the right Zero-Chase trigger and threshold
- Approve, reject and evaluate automation work
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.