Where to start
Admin Area → Property Management Flow → Zero-Chase → Approval & execution queue
Before you begin
Evaluate active rules can both queue candidates and execute work that is eligible to run. Review the rule and intended recipients before using it.
Follow these steps
- Preview the active rule and check its actions.
- Choose Evaluate active rules to create eligible candidates and process due approved or automatic work.
- In the queue, inspect items awaiting approval.
- Choose Approve only for the intended action, or Reject to stop that awaiting-approval item.
- Allow the next scheduled cycle or evaluate again to process eligible approved work.
- Check both the queue status and each action in Execution audit log.
Check the result
Approved items move into pending processing; rejected items are recorded as rejected. The action log gives the individual outcomes.
If something does not look right
An approval can be refused if the item is no longer awaiting approval or your underlying permissions changed. Refresh the screen before retrying.
Questions and answers
Does Approve immediately send the email?
Approval makes the item eligible for a processing cycle. Processing occurs through evaluation or cron when due.
Does Completed prove delivery?
No. A queue item can complete while an individual action is logged not_delivered. Inspect each action outcome.
Does disabling the rule cancel already queued work?
No cancellation is performed by the enable/disable control. It stops new active-rule evaluation; existing pending work needs separate operational review. Do not assume disabling revokes earlier approvals.
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
- Investigate automation recipients, failures and retries
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.