Error overview

You may run into this Salesforce validation error when deploying a FlexiPage metadata type.

In Gearset the error message would be reported as below:

"Component [force:highlightsPanel] attribute [actionNames]: We couldn't validate Custom Action <xxx>" - where <xxx> refers to a specific Quick action or Web lightning component metadata.

Explanation of the error

Based on our understanding, Salesforce is asking to add the referenced Custom action (Quick action metadata type) or the Web lightning component, into the deployment package.

Resolution

Below we're explaining how to resolve the error depending on how you're making your deployment in Gearset.

Workaround for failed PR validation in Gearset Pipeline

To resolve the error when a pull request in your Gearset Pipelines fails the validation:

Check if you can deploy the referenced Custom action into the target org as part of a separate PR. Once done, you can re-validate the existing PR.
If the above isn't possible, add the Custom action (referenced in the error message) into the feature branch from which your original PR was created.
In your Gearset Pipeline, you can do it by selecting the Dev Sandbox from which feature was created, and then selecting Commit more changes...

Note: Make sure to commit changes to the correct feature branch!
Once the missing item is committed, you can re-validate the PR in your Pipeline.
Guidelines on how to add more changes to an existing feature branch can be found in this article: Promoting your first features.

Note: If the Custom Action is related to a Lightning Web Component (LWC), confirm that the LWC is also deployed and available in the target org.

Other possible root cause:
It's possible that either the FlexiPage you're deploying, or LWC that Custom action is related to (or both) are related to or depend on an Apex class that is missing in the target org.

In this case ensure the Apex class is present in the target org before you proceed with the deployment.

Workaround for deployments made via Compare and deploy

Does the error happen when running a direct Compare and deploy validation? (e.g. Git to org, or org to org) validation?

For Git to org deployments

You can use our "Compare and deploy" feature to commit the missing Quick action, or Lightning web component, to the branch from which you were originally deploying the FlexiPage. Then validate it against the target org.

For org to org deployments

Make sure your metadata filter includes and have retrieved both Quick action and Lightning page metadata types.
Then add the missing Quick action or Lightning web component into the deployment package.
Once done, validate against the target org.

Useful sources

For more information on this error check the Trailblazer Community threads: source1, source2 and source3.

Disclaimer: This error is returned by Salesforce directly, rather than Gearset. Even so, we offer guidance based on our combined experience with the Metadata API. Where possible, we try to help guide you to fix or avoid this error. In the case that this isn't possible, we may need to direct you to Salesforce support for further clarification.

Resolving validation errors - "<xxx> does not exist or is not a valid override for action <yyy>"

Resolving validation errors - "Invalid property <xxx> in component <yyy>"

Resolving validation errors - "The CustomObjectTranslation called <xxx> is standard and cannot be deleted"

Resolving validation errors - "<xxx> isn't a valid value for Conditional Formatting."

Resolving validation errors - "Invalid field: SOLUTION.ISSUE in related list: RelatedSolutionList" on Layout metadata type