Configure emails per cron run | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/customer-surveys-feedback-management-batch-setting Publisher: Pixie Technologies LLC Setup, access and permissions Configure emails per cron run 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 set survey_send_emails_per_cron_run; the installed default is 100. Audience: CRM administrators, marketing teams, service managers and authorised staff; Permission: Administrator; Module v2.3.0; Where to goAdmin Area → Setup → Settings → Surveys Before you start - Verify the module is active and use the exact navigation shown above. - Use an account with the stated module and core CRM permissions. - Use known test records when changing statuses, visibility, saved filters or global navigation. What this guide helps you do Set survey_send_emails_per_cron_run; the installed default is 100. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow. Follow these steps - Go to Admin Area → Setup → Settings → Surveys. - Select the record or action required for configure emails per cron run. - Complete the displayed fields and choices described in this guide. - Save, submit, approve or confirm the action as shown on screen. - Refresh the relevant list, record or report and verify the expected result. Fields and options WorkspaceAdmin Area → Setup → Settings → Surveys ActionSet survey_send_emails_per_cron_run; the installed default is 100. Rules and limits - Only controls rendered by the supplied module are documented; hidden AJAX helpers are mapped to their visible parent workflow. - Core CRM record permissions and module permissions are both enforced where the code checks them. Check it worked - The configure emails per cron run action completes without a validation or permission error. - The affected record, stock balance, response, session or style reflects the saved state. - Audit, notification, report or portal evidence appears only where the module code creates it. Security, privacy and operational checks - Use a controlled test record before applying changes to live inventory, recipients, visitor tracking or global styling. - Grant only the minimum module and core CRM capabilities needed for the task. Related guides Create a survey from the quick action (https://pixiecrm.com/help-centre/customer-surveys-feedback-management-quick-action)Understand the last survey-send cron value (https://pixiecrm.com/help-centre/customer-surveys-feedback-management-last-cron)Setup, access and permissions (https://pixiecrm.com/help-centre/topic/customer-surveys-setup-access)Browse all Customer Surveys & Feedback Management guides (https://pixiecrm.com/help-centre/category/customer-surveys-feedback-management)Customers and contacts (https://pixiecrm.com/help-centre/category/customers-contacts)Leads and pipeline (https://pixiecrm.com/help-centre/category/leads-pipeline)Email and communications (https://pixiecrm.com/help-centre/category/email-communications)Reports, goals and surveys (https://pixiecrm.com/help-centre/category/reports-goals-surveys)Data, privacy and security (https://pixiecrm.com/help-centre/category/data-privacy-security)Advanced Task Filters (https://pixiecrm.com/help-centre/category/advanced-task-filters)