Scheduled Jobs

Who this is for

IT admins and compliance leads who want recurring governance tasks to run automatically, without manual triggering each time.

Before you start

You need the Admin role or higher to create and manage scheduled jobs. Jobs that involve actions in connected systems require at least one active connector.

What scheduled jobs are

A scheduled job is a recurring governance task that runs automatically at a defined interval. Jobs can run evaluations, trigger reports, initiate access reviews, or execute approved workflow actions on a cadence you set. Every job execution is recorded as an audit event whether it succeeds, fails, or is skipped.

What you can schedule

• ·Control pack evaluations: Run a specific control pack on a weekly or monthly cadence so findings are always current.
• ·Access reviews: Trigger a periodic access certification campaign for a group, department, or connected system.
• ·Report generation: Automatically generate and deliver a compliance or usage report to designated recipients.
• ·License reconciliation: Run a license usage check at a set interval to catch waste before renewal windows.
• ·Connector sync: Force a sync of a specific connector on a schedule, in addition to its default polling interval.
• ·Chat-to-Action plans: If your team creates action plans through Chat-to-Action, those plans can be scheduled to execute automatically after an initial approval.

How to create a scheduled job

1. 1In Nuxari, go to Platform > Scheduled Jobs.
2. 2Click New Scheduled Job.
3. 3Select the job type and configure the specific target, for example, which control pack to evaluate or which report to generate.
4. 4Set the schedule: daily, weekly, monthly, or a custom cron expression.
5. 5If the job triggers actions in connected systems, assign an approver who must authorize each execution before it runs.
6. 6Save the job. It will execute at the next scheduled time.

How to monitor job history

1. 1In Nuxari, go to Platform > Scheduled Jobs.
2. 2Select a job to view its execution history.
3. 3Each run shows its start time, duration, status (Completed, Failed, Skipped, or Pending Approval), and the audit event reference.
4. 4Click a run to view the full execution log and any errors that occurred.

Job statuses

• ·Scheduled, the job is active and will run at the next scheduled time.
• ·Running, the job is currently executing.
• ·Pending Approval, the job ran but requires authorization before the action executes in a connected system.
• ·Completed, the job finished successfully. All associated actions are recorded.
• ·Failed, the job encountered an error. Review the execution log for details.
• ·Skipped, the job was due to run but was paused or a dependency was unavailable.
• ·Paused, manually paused by an admin. The job will not run until resumed.