Skip to main content
Validation checks are an internal step of Concord. After Concord builds a platform action and before it shows it to you, it checks the action against the platform’s rules. You do not start this step, configure it, or approve it, and it has no screen of its own: you only see its result when a problem remains. The point is that what you review is already coherent with the platform’s rules, so approving is a decision about intent, not a proofreading exercise.

Where it happens

  1. You ask for a change and Concord builds the platform action.
  2. Concord validates it, automatically. It checks each object, then the objects that belong together, then that the request can be built for the platform.
  3. You review the platform action and approve it.
  4. Concord submits it to the platform.

What gets checked

Required fields: every field the platform requires for that object type and campaign type, at every tier of the tree. Coherence: budgets against flight dates, start dates against end dates, child objects against their parent’s configuration. Platform rules: allowed objectives, valid bid strategy and budget combinations, formats and character limits. Quotas and limits: anything the platform caps, such as the number of targeting criteria on an object. Availability for this account: targeting values are resolved against what your advertiser can actually target, rather than assumed.

What Concord fixes on its own

Some corrections are unambiguous, so Concord applies them without asking. They are not reported as warnings: you see the corrected values when you review the action.
  • Forcing a newly created object to a non-active status
  • Renaming a duplicated object so the name stays unique
  • Completing a field the platform derives from another one you set
  • Dropping a targeting value that is not available in every country you are targeting

What Concord comes back to ask

When a fix would be a guess about your intent, it asks instead of choosing:
  • A required field the brief does not cover and your rules do not default
  • A budget or date that contradicts one of your Skills
  • A platform rejection that has more than one reasonable resolution

What you see

  • When the checks pass, nothing. There is no “checks passed” indicator.
  • When a problem remains, a warning icon appears next to the affected action. Hover it to read the field and the message.

When a check fails

The action is not submitted. Concord corrects it and validates it again. After three failed attempts on the same action within one request, it stops and shows you the errors rather than retrying indefinitely. You can also correct it in the conversation and Concord prepares the action again.

After you approve

Validation does not replace the platform’s own checks. A platform can still reject an action at submission. The action then shows the platform’s error, and the Submit button becomes Retry.
The most common source of avoidable failures is a rule that lives in someone’s head. Once a check fails for the same reason twice, put it in a Skill. Concord applies your Skills when it prepares the action, so the next one arrives already following the rule.