The learner must configure an n8n workflow with conditional validation and error handling using the Stop and Error node to halt execution when invalid budget data is detected. The student's n8n workflow MUST include ALL of the following: 1. **Workflow Import**: The workflow file `2.4.3_customer_errors` is imported and executed from the Resources folder 2. **Conditional Validation**: An `If` node is connected after the `Code` node with conditions that check THE BUDGET FIELD: - budget is less than 0 (zero) OR - budget is empty (Note: The logical operator between conditions must be OR, not AND) (Critical: The If node must validate the BUDGET field specifically, not other fields like project, amount, price, etc.) 3. **Error Routing**: The `false` branch of the `If` node is connected to a `Stop and Error` node (the false branch represents records that fail validation) 4. **Custom Error Message**: The `Stop and Error` node is configured with a custom error message that communicates budget validation failure. Acceptable messages include but are not limited to: - "Invalid record - budget doesn't meet criteria" (template wording) - "Invalid record: budget doesn't meet criteria" - "Invalid record - budget criteria not met" - "Budget validation failed" - "Budget validation error" - "Budget does not meet criteria" - "Invalid budget detected" - Any other clear message indicating budget validation failure (Note: Generic default messages like "An error occurred!" do NOT satisfy this requirement) 5. **Workflow Execution**: The complete workflow is executed and produces the expected error with the custom message 1. The learner opens and examines the Execution Details panel to view the custom error message 2. The learner verifies that exactly 4 records are identified by the false branch 3. The learner uses proper expression syntax for accessing the budget field from input data 4. The learner understands the difference between the true and false branches in conditional routing **Evaluation Priority: Output-First Approach** **Step 1: Evaluate Workflow Execution Result** First, execute the n8n workflow and observe the behavior. ✅ PASS if the workflow execution demonstrates ALL of the following: - The workflow stops/halts when processing records with invalid budget data (budget < 0 or empty) - A `Stop and Error` node is triggered (visible in execution flow) - The error banner/message displays a CUSTOM message related to budget validation failure (not the default "An error occurred!"). Acceptable messages include "Invalid record - budget doesn't meet criteria", "Budget validation failed", "Budget validation error", "Invalid budget detected", or any semantically equivalent message that clearly indicates budget validation has failed - The If node conditions are actually checking the BUDGET field (not other fields like project, amount, price, etc.) with the logic: budget < 0 OR budget is empty - The workflow correctly identifies records that fail budget validation (approximately 4 records on the false branch: records with negative budgets or empty/null budgets) **CRITICAL**: Even if the workflow triggers a Stop and Error node with the correct message, it must FAIL if the If node is checking the wrong field or using different validation logic. For example, checking if "project contains Mobile" or "amount < 100" instead of "budget < 0 OR budget is empty" is incorrect and must fail. If the workflow behaves as described above—stopping on invalid budget data, displaying a custom error message, AND validating the correct budget field with the correct conditions—PASS the learner. The functional error handling demonstrates sufficient understanding of validation and error node configuration. **Step 2: If Workflow Does Not Execute Correctly, Evaluate Configuration** Only if the workflow fails to execute properly or doesn't stop on invalid data, examine the workflow configuration: ✅ PASS if the configuration shows: - `If` node is present and connected after the `Code` node - Conditional logic checks THE BUDGET FIELD specifically (using expressions like `{{ $json.budget }}` or equivalent) with conditions: budget < 0 OR budget is empty (using OR operator, not AND) - `Stop and Error` node is connected to the false branch of the `If` node - Error message is configured with CUSTOM text related to budget validation (not the default "An error occurred!"). The exact wording can vary as long as it clearly communicates budget validation failure (e.g., "Budget validation failed", "Invalid budget", "Budget doesn't meet criteria", etc.) - Workflow structure indicates proper understanding even if execution had minor issues ❌ FAIL if: - No `If` node present or not properly connected after `Code` node - **Conditional logic checks the WRONG FIELD** (checking project, amount, price, or any field other than budget) - this is a critical failure even if the workflow structure looks correct - Conditional logic checks the budget field but uses incorrect operators or conditions (e.g., only checking < 0 without checking empty, or using AND instead of OR) - Conditional logic is incomplete (missing one of the two required conditions: budget < 0 or budget is empty) - `Stop and Error` node is missing or connected to wrong branch (connected to true branch instead of false) - No custom error message configured (still using default "An error occurred!" or similar generic message), OR error message is completely unrelated to budget validation - Workflow structure shows fundamental misunderstanding of error handling pattern **Note:** Prioritize functional outcomes over perfect configuration details, BUT the If node MUST validate the budget field with the correct conditions (< 0 OR empty). If the workflow successfully stops on invalid data but is checking the wrong field or using different validation logic, it must FAIL. The specific wording of the error message can vary as long as it clearly communicates budget validation failure and is not the generic default message. FEEDBACK GUIDELINES: - **For PASS via execution**: "Excellent work! Your workflow correctly validates budget data and stops execution with a clear custom error message when invalid records are detected. This prevents bad data from propagating through the system." - **For PASS via configuration**: "Your workflow configuration is correct—the If node logic and Stop and Error setup are properly structured. The validation rule correctly checks for negative or empty budget values. [If applicable: There may be a minor execution issue to troubleshoot, but your understanding of the error handling pattern is solid.]" - **For FAIL**: Identify specific gaps: - If If node is missing: "The workflow needs a conditional validation step using an If node to check budget values before they proceed." - **If wrong field is being validated**: "The If node must validate the BUDGET field specifically, not [field name]. The exercise requires checking if budget is less than 0 OR is empty. Currently your workflow is checking [describe what field/condition is configured]." - If conditional logic is wrong: "The If node conditions should check if budget is less than 0 OR is empty (using OR, not AND). Currently [describe what's configured]." - If conditions are incomplete: "The If node needs BOTH conditions: (1) budget is less than 0, AND (2) budget is empty, connected with OR operator. Currently [describe what's missing]." - If Stop and Error is on wrong branch: "The Stop and Error node should be connected to the FALSE branch (records that fail validation), not the true branch." - If error message is generic/default: "Configure a custom error message in the Stop and Error node to provide clear feedback about budget validation failure. Replace the default 'An error occurred!' with a message like 'Invalid record - budget doesn't meet criteria' or 'Budget validation failed'." - If error message is unrelated to budget: "The error message should specifically indicate budget validation failure, not [describe what's configured]." - Explain why correct error handling matters: "Proper validation prevents invalid data from reaching your CRM, which would cause campaign failures and support issues. The validation must specifically check the budget field to catch the data quality problems described in the exercise."

Pruebas y validación de flujos de trabajo

Create Your Free Account