MAG OptiAI

Data and runs How-To

How to read validation errors

Understand what validation messages mean, where to find them, and how to fix your data or setup before continuing in MAG OptiAI Pro Console.

Read stepsAll How-To Guides

Guide details

Audience

Product users

Time

4 minutes

Category

Data and runs

What this guide covers

Understand what validation messages mean, where to find them, and how to fix your data or setup before continuing in MAG OptiAI Pro Console.

Understand what validation errors mean

Find which input or file has the issue

Read severity, message, location, and suggested fix

Identify the affected field, column, row, or value

Review the expected format or missing requirement

Fix the source file and upload it again

Upload again and confirm readiness

Validation setup

What is a validation error?

Use this section to understand what validation errors mean before you fix your data. A validation error appears when the system finds missing, incorrect, duplicated, or unsupported information in your uploaded file or scenario setup.

What a validation error may point to

A missing required file, missing column, empty required value, wrong date or number format, duplicate ID, special character, or mismatched record.

Important

A warning should still be reviewed, even if it does not block the next step.

Step by step

Follow the task path

Each step gives you the action, the reason it matters, and the visual state to look for before continuing.

1

Step 1

Understand what a validation error means

ValidationData issues

A validation error appears when uploaded data or setup values cannot be safely used by the workspace. It tells you what the system found and what must be fixed before continuing.

What is a validation error?

A validation error is a message that tells you something in your data does not match the required input rules for the selected product.

It may appear when a file is missing, a column name is incorrect, a required value is empty, a format is wrong, or a value does not connect correctly with another input.

Before continuing, read the validation message carefully.
It helps you know what needs to be fixed before the scenario can be tested or released.

A validation error may point to:

Missing required file

Missing column

Empty required value

Wrong date or number format

Duplicate ID

Unsupported reference

(product, job, machine, route, or document)

Next step: Follow the steps in the next section to resolve validation errors.

2

Step 2

Follow the fix flow

When you get a validation error, move through the same fix flow each time: check the affected input, identify the exact location, review the expected requirement, fix the source file, and upload again.

Fix flow

What to do when you get a validation error

When a validation error appears, do not continue to release testing immediately. Use the error message to locate the issue, correct the source data, and confirm that the setup is valid again.

1

Check the affected input or file

Identify which file or input area caused the error.

Examples

  • Jobs file
  • Machines file
  • Products file
  • Calendar file
  • Demand file
  • Routes file
  • Documents
  • Scenario setup input
2

Identify the exact location

Check the details in the error message to find the exact column, row, field, value, or record.

The message may point to:

  • Column name
  • Row number
  • Field
  • Missing value
  • Duplicate ID
  • Specific record or reference
3

Review the expected requirement

Read what the system expected from that field or value.

The error may ask for:

  • Required column
  • Valid date format
  • Numeric value
  • Unique ID
  • Supported reference
  • Required value that cannot be empty
4

Fix the source file

Make the correction in the original CSV file or source data.

Examples

  • Add the missing column
  • Fill the empty value
  • Correct the date format
  • Remove duplicate IDs
  • Replace unsupported references
  • Ensure related files use matching IDs
5

Upload again and recheck

Upload the corrected file again and return to the validation status.

Make sure the error is cleared before continuing to release testing.

Important: Always fix the source file, upload the corrected version, and recheck the validation status. A scenario should only move forward when required inputs are valid and there are no blocking errors.

3

Step 3

Read the validation message

SeverityInputLocationHow to fix

Each validation message gives you clues about what went wrong and where to fix it. Start by reading the severity, input or file, message, location, and how-to-fix guidance.

Example validation messages

ErrorJobs.csv
Message
Missing required value in column Release Date.
Location
Row 42 / Release Date
How to fix
Add a valid release date.
WarningMachines.csv
Message
Duplicate value M03 found in Machine ID.
Location
Rows 12, 35 / Machine ID
How to fix
Use a unique machine ID.
1

Severity

Shows whether the issue is blocking (error), warning, or informational.

2

Input or file

Shows which uploaded file or input area contains the issue.

3

Message

Explains what the system found, such as a missing value, invalid format, or unsupported reference.

4

Location

Points to the row, column, field, or record where the issue appears.

5

How to fix

Gives the correction needed before you upload the file again.

Tip: Do not fix the data based only on the error title. Always check the file, location, and expected correction before editing the source file.

4

Step 4

Confirm readiness before continuing

Before continuingReadiness

Before moving forward, make sure all blocking validation errors have been removed. The scenario should only continue when the required inputs are valid and the setup readiness review shows no issues that prevent testing or release.

If an error is still visible, go back to the source file, correct the data, upload the updated version, and review the validation status again.

Your setup is ready when:

Required files are uploaded

All required input files are attached.

Blocking errors are cleared

No blocking validation errors are shown.

Required columns and values are valid

All required columns exist and contain valid values.

Related inputs connect correctly

IDs, references, and relationships match across all inputs.

Validation status has been reviewed

You have reviewed the latest validation status after your updates.

Readiness reminder
Do not continue to release testing until the validation status is clear. Fix the source data, upload the corrected file, and confirm the setup is ready.

Tips

Fix blocking errors before warnings.
For multi-file products, ID mismatches across files are common.
Do not run until the readiness section says the required setup is ready.

Related links

Input SpecsContact Support

Related how-to guides

Continue with nearby tasks in the same category.

How to prepare your scenario

Before you upload files or run a workflow, define the scenario you want to solve and make sure your data matches the selected MAG OptiAI workspace.

Open guide

How to prepare and upload your data

Use this checklist to prepare your data before moving to configuration. Open the input spec, match the required format, upload your files, and confirm the workspace is ready.

Open guide

How to configure and run optimization or scoring

Review your configuration, choose the right solver or scoring settings, run the process, and check the results inside the MAG OptiAI Pro Console.

Open guide

Next

Keep moving through MAG OptiAI resources

Return to the full how-to library or step back to the resource hub when you want a different kind of guide.

All How-To GuidesBack to Resources