Understand the fine-tuning job suffix | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-the-fine-tuning-job-suffix Publisher: Pixie Technologies LLC Fine-tuning job lifecycle Understand the fine-tuning job suffix Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Identify module-created jobs and models. Audience: CRM administrators and authorised staff; Permission: Technical administrator; Module v1.0.0; Where to goCode-backed reference → OpenAI fineTuning createJob Before you start - Use an account with Technical administrator and confirm the intended record or setting before making a change. - Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account. - Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use. What this guide helps you do Identify module-created jobs and models. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow. Follow these steps - Go to Code-backed reference → OpenAI fineTuning createJob. - Select the relevant record, filter, report, model or configuration described below. - Use the displayed action or read the current values without altering unrelated data. - Compare the output with the code-backed rules and expected result in this guide. - Record or correct any mismatch before relying on the output in production. Fields and options ActionUnderstand the fine-tuning job suffix Exact navigationCode-backed reference → OpenAI fineTuning createJob Module version1.0.0 VerificationVerify the saved record, status, output or setting in the same workspace and review any linked activity, file or notification. Rules and limits - The suffix is pcrm- followed by the current YYYYMMDD date. - The pcrm marker is also used to identify module-owned models. Check it worked - The supported understand the fine-tuning job suffix flow completes without bypassing permission or validation checks. - The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace. - Unexpected validation, provider or linked-record errors are investigated before retrying. Security, privacy and operational checks - Restrict the API key and AI settings to authorised administrators. - Do not submit confidential, special-category or unnecessary personal data to the external AI provider. - Check generated text before using it in customer, staff, legal, financial or compliance communication. - Monitor provider billing and retention independently because this module has no built-in cost dashboard. Related guides Understand the OpenAI training-file upload (https://pixiecrm.com/help-centre/understand-the-openai-training-file-upload)Review saved fine-tuning job and file identifiers (https://pixiecrm.com/help-centre/review-saved-fine-tuning-job-and-file-identifiers)Start an OpenAI fine-tuning job (https://pixiecrm.com/help-centre/start-an-openai-fine-tuning-job)Open the OpenAI fine-tuning workspace (https://pixiecrm.com/help-centre/open-the-openai-fine-tuning-workspace)Review available fine-tuned OpenAI models (https://pixiecrm.com/help-centre/review-available-fine-tuned-openai-models)Browse all OpenAI Integration guides (https://pixiecrm.com/help-centre/category/openai-integration)Enterprise Integrations (https://pixiecrm.com/help-centre/category/enterprise-integrations)Data Privacy Security (https://pixiecrm.com/help-centre/category/data-privacy-security)Support Knowledge (https://pixiecrm.com/help-centre/category/support-knowledge)