Run and verify the cron job | Pixie CRM Help Centre
Canonical: https://pixiecrm.com/help-centre/run-and-verify-the-cron-job
Publisher: Pixie Technologies LLC

How-to guide
Run and verify the cron job

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to configure scheduled processing for reminders, recurring records, email and automation.

Audience: Administrator; Feature: Setting; Permission-aware; 

Where to goSetup → Settings → Cron Job / Utilities

Before you startThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.

What this guide helps you do

Configure scheduled (https://pixiecrm.com/help-centre/topic/scheduling) processing for reminders (https://pixiecrm.com/help-centre/topic/reminder), recurring records, email (https://pixiecrm.com/help-centre/topic/email) and automation. Pixie CRM keeps the result connected to the relevant customer (https://pixiecrm.com/help-centre/topic/customer), staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal (https://pixiecrm.com/help-centre/topic/client-portal) visibility and future automation.

Follow these steps

- Go to Setup → Settings → Cron Job / Utilities using an administrator or appropriately permitted account.

- Check the current value and understand which users, records or automated processes it affects.

- Enter or select the new configuration values. Keep labels concise and use the approved business terminology.

- Where credentials, email (https://pixiecrm.com/help-centre/topic/email), webhooks or cron are involved, begin with a test or sandbox configuration.

- Save the change and confirm that Pixie CRM reports (https://pixiecrm.com/help-centre/topic/report) success.

- Test the affected workflow with a non-critical record and with a restricted user where permissions are relevant.

- Document the operational change and use the available reset or rollback option if the result is not correct.

Settings to check

Setting nameCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Enabled statusCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Scope or audienceCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Order or positionCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Display labelCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Reset or fallback behaviourCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.

Checks before you finish

- Change only one area at a time.

- Record the previous value.

- Verify desktop and mobile behaviour after saving.

- Check (https://pixiecrm.com/help-centre/topic/check) whether the result should be visible to a customer contact (https://pixiecrm.com/help-centre/topic/customer) or only to staff.

- Confirm the final status, activity entry, generated document or notification (https://pixiecrm.com/help-centre/topic/notification) before leaving the record.

Permission and data safetyDeletion, refunds, signature clearing, module changes, payment (https://pixiecrm.com/help-centre/topic/payment) configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval (https://pixiecrm.com/help-centre/topic/approval) process.

Browse connected topics:invoice (https://pixiecrm.com/help-centre/topic/invoice)payment (https://pixiecrm.com/help-centre/topic/payment)expense (https://pixiecrm.com/help-centre/topic/expense)check (https://pixiecrm.com/help-centre/topic/check)report (https://pixiecrm.com/help-centre/topic/report)approval (https://pixiecrm.com/help-centre/topic/approval)scheduling (https://pixiecrm.com/help-centre/topic/scheduling)client portal (https://pixiecrm.com/help-centre/topic/client-portal)reminders (https://pixiecrm.com/help-centre/topic/reminder)notifications (https://pixiecrm.com/help-centre/topic/notification)email (https://pixiecrm.com/help-centre/topic/email)customers (https://pixiecrm.com/help-centre/topic/customer)custom fields (https://pixiecrm.com/help-centre/topic/custom-field)

Related guides

Schedule an invoice email (https://pixiecrm.com/help-centre/schedule-an-invoice-email)Schedule an estimate email (https://pixiecrm.com/help-centre/schedule-an-estimate-email)Prepare Pixie CRM for production use (https://pixiecrm.com/help-centre/prepare-britixo-crm-for-production-use)Create a recurring expense (https://pixiecrm.com/help-centre/create-a-recurring-expense)Configure email piping for tickets (https://pixiecrm.com/help-centre/configure-email-piping-for-tickets)