Error 422 when trying to trigger GitHub workflows from Allure TestOps

Created by George I., Modified on Mon, 22 May 2023 at 02:57 PM by George I.

Server (in this case it's GitHub) returns the error 422 when it cannot process the received request.

In the vast majority of cases this means you are sending some parameters which aren't known to the remote server.

In scope of the integration with GitHub this most likely means we're trying to set  GitHub workflow's parameters which are absent in the workflow.

To resolve the issue, you need to check if you added all parameters required for Allure TestOps to be able to trigger a workflow:

There is a set of mandatory parameters starting with ALLURE_ required to run the workflow. If any of the parameters starting with ALLURE_ will be missing in the inputs section, then the attempts to execute such a workflow from Allure TestOps will fail with the error 422.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article