> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/email-this-issue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/email-this-issue/email-this-issue-for-jira-server-data-center/faq/faq/how-to-bypass-workflow-conditions.md).

# How to bypass workflow conditions

### Description

When trying to run workflow transitions based on incoming emails, they may fail seemingly unexpectedly.

A strange line offers little to no explanation in the incoming mail log:

**WARN: Could not execute transition**.

<figure><img src="/files/uMqQwIpSt4aZnNMWSdE2" alt=""><figcaption><p>Email log excerpt for transition warning log</p></figcaption></figure>

This is only visible when you try to run a workflow transition via the [Execute workflow transition](https://docs.meta-inf.hu/email-this-issue/v/email-this-issue-for-jira-server-data-center/documentation/incoming-emails/mail-handlers/next-generation-mail-handlers#nextgenerationmailhandlers-executeworkflowtransitionexecutetransitionaction) action of the mail handler.

The reason behind is that Jira cannot run a transition with our app if there is a condition present, therefore the mail handler action will return with the above message.

### Workaround

There is no out-of-the-box solution in Email This Issue for bypassing workflow conditions.

A way to work around this limitation is to combine automations with Email This Issue actions.

In case of running a transition on an existing issue, the following example may be of help.

#### Example

In a nutshell, you need to set up an automation that gets triggered after a comment is made by the mail handler and that which looks for the same criteria you are using in the mail handler (for example a regular expression).\
&#x20;If it matches the conditions, the automation runs the transition instead of Email This Issue.

Let us look at an example process:

1. An email is sent to the mail handler's address and is processed by our application
2. Email this issue makes a comment on the existing ticket it finds
3. An automation gets triggered due to a comment being added \
   The automation has 3 conditions:
   1. Initiator is the same account as the default reporter in the mail handler
   2. The issue has a specific component (which is also set by the mail handler when first creating the issue)
   3. The regular expression is matched towards the email
4. If above conditions are met, the automation transitions the issue to the desired state


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.meta-inf.hu/email-this-issue/email-this-issue-for-jira-server-data-center/faq/faq/how-to-bypass-workflow-conditions.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.