Reference: Background Jobs
This reference covers the background jobs that AccessHive runs to provision identities, sync directories, and automate workflows. Jobs run on a separate worker process and do not block the main application.
Job types
| Job type | Description | Triggered by |
|---|---|---|
| Create domain user | Creates a user in Google Workspace (GWS) | Creating a Human Interactive or managed Shared Credential identity on a GWS platform |
| Provision identity provider user | Provisions a single sign-on (SSO) user in the identity provider | Creating a Human Interactive identity |
| Credential rotation | Rotates the password after a Privileged Access Management (PAM) session ends | PAM session check-in |
| Directory sync | Synchronizes users and groups from an identity source | Manual trigger or scheduled run |
| Audit ingestion | Imports audit logs from connected platforms | Scheduled run |
| Asset discovery | Discovers resources on a connected platform | Manual trigger |
| Bulk import | Processes a CSV bulk import file | Bulk import upload |
| Joiner/Mover/Leaver automation | Runs automated workflows when directory changes are detected | Directory change event |
| Remediation | Runs an auto-remediation action in response to a policy violation | Policy violation detected |
Job lifecycle
Every background job moves through these statuses:
| Status | Meaning |
|---|---|
| Pending | The job is queued and waiting for the worker to pick it up. |
| Running | The worker is actively processing the job. |
| Completed | The job finished successfully. |
| Failed | The job encountered an error. |
| Retrying | The job failed and is being retried with increasing wait time between attempts. |
Job settings
| Setting | Default | Description |
|---|---|---|
| Maximum attempts | 5 | Number of retry attempts before permanent failure. |
| Backoff strategy | Exponential | The wait time between retries doubles after each attempt. |
| Timeout | 120 seconds | Maximum time allowed for a single attempt. |
Which identity types trigger jobs
Not all identity types require background jobs. Types that carry their own credentials are stored immediately and marked as Provisioned without waiting for a job.
| Identity type | Creates domain user | Provisions SSO user | Result |
|---|---|---|---|
| Human Interactive (GWS platform) | Yes | Yes | GWS user and SSO user created |
| Shared Credential – managed (GWS platform) | Yes | No | GWS user created, SSO skipped |
| Shared Credential – external (any platform) | No | No | Instant – credentials stored in the vault |
| Service Account (any platform) | No | No | Instant – JSON key stored in the vault |
| API Key (any platform) | No | No | Instant – key stored in the vault |
| OAuth Client (any platform) | No | No | Instant – credentials stored in the vault |
Identity types that carry their own authentication (Service Account, API Key, OAuth Client, and external Shared Credential) never trigger background jobs. Their credentials are stored in the Credential Vault immediately and the identity is marked Provisioned right away.
For a full explanation of identity types, see Identity Types.
Monitoring jobs
Navigate to Settings > Jobs to view the job dashboard. The dashboard shows:
- Job list – filtered by type and status
- Timing – when the job was created, started, and completed
- Input data – the identity and user who triggered the job
- Result – output from successful jobs
- Error details – error messages for failed jobs
- Retry – a button to manually retry failed jobs
Related pages
- Provisioning States – all provisioning statuses and transitions
- Identity Field Requirements – required fields per identity type
- Creating Identities – step-by-step identity creation guide
- Google Workspace Guide – GWS setup, provisioning, and sync
- Troubleshooting – common issues and fixes