# Continue On Error

| Attribute           | Type    | Description                                                                                              | Package Types Applicable                                                              |
| ------------------- | ------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **continueOnError** | boolean | Record validation/test/coverage failures for this package but do not fail the overall `sfp validate` run | <ul><li>unlocked</li><li>org-dependent unlocked</li><li>source</li><li>diff</li></ul> |

By default, a single package failing validation (deployment, apex tests, or coverage) fails the entire `sfp validate` run. The `continueOnError` package descriptor lets you opt out of that behaviour for a specific package — failures are still surfaced in the validation output (and the validation-error.md report), but they do not flip the run's exit code.

This is useful when a package is in transition (e.g. a legacy component being refactored, or a flaky test suite that's already tracked separately) and you want validate to keep checking the rest of the project rather than short-circuiting on that one package.

<pre class="language-json"><code class="lang-json">// Demonstrating how to use continueOnError
{
  "packageDirectories": [
    {
      "path": "legacy-reports",
      "package": "legacy-reports",
      "versionDescription": "Legacy reporting package being refactored",
      "versionNumber": "2.1.0.NEXT",
      <a data-footnote-ref href="#user-content-fn-1">"continueOnError": true</a>
    },
     ...
   ]
}
</code></pre>

{% hint style="warning" %}
Use this attribute deliberately — it can hide real regressions. Pair it with an issue tracker reference so the underlying failure isn't forgotten.
{% endhint %}

[^1]: Allow this package's validation failure to be recorded without failing the overall validate run


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flxbl.io/flxbl/sfp/sfp-community/validating-a-change/controlling-validation-attributes-of-a-package/continue-on-error.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.