Check scheduled compliance processing

Verify scheduled property synchronisation, notifications and the separate retention results.

Before you start

Compliance View opens the workspace; Create is used for new intake, Edit for review/approval and Delete for deletion. Each action also validates its record.

Follow these steps

1. Ask the administrator to verify the host scheduler is running for the intended workspace.
2. Open Compliance → Core Compliance → Notification / Intimation Engine and check recent processing and delivery results.
3. Check source relationships in Synced Compliance Index if records are missing.
4. Inspect retention results separately; optional compliance retention and tenant-application retention have different enablement conditions.

Fields, rules and limits

• The merged module runs compliance work through the host scheduler with a per-workspace lock. An authorised manual run uses the same notification service. A protected cron endpoint also exists; administrators must keep its configured key private and check the returned run results.

Check it worked

The linked entity, saved state, dates and evidence match the intended task.

If something does not look right

If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.

Questions and answers

Does a parsed document count as approved?

No. Parsing supplies suggested values. A reviewer must verify the linked entity, evidence and required fields, then use the separate approval action.

Is the generated PDF the original certificate?

No. The system PDF reflects the saved compliance record or notification. Open the original source evidence separately when checking the document supplied.

Useful next steps

• Find the current module menus
• Browse all merged module guides