Flower Help

Troubleshooting and Support

Most of our FAQs can be found on the relevant pages of the Purchasing & Admin or How-To section. If you can’t find the answer you’re looking for, please reach out to our Customer Support Team and we’ll be happy to help.

What does this error message mean?

“500 - Duplicate key” or “Duplicate field reference error”

The most common cause of a 500 error is a field that is added to several tabs of the same screen. Jira does not permit this.

To fix it, you need a Jira administrator:

Find the duplicated field and its screen.

In Jira Data Center, follow the steps in this Atlassian Knowledge Base article . It requires SQL access to your Jira database.
In Jira Cloud, check the screens of the work type that causes the error.

Open the screens in the Jira administration. In Jira Cloud, go to Settings > Work items > Screens. In Jira Data Center, go to Administration > Issues > Screens.
Look for the screen from the result, for example “SSD: Scrum Default Issue Screen”.
Click Configure and look for the field, for example “assignee”.
Remove one of the duplicate entries from the screen.

If the screen has several tabs, check every tab for the field.

”500 - Internal Server Error”

These errors are most commonly caused by Jira, not by Flower. Flower stores its process data in Jira and loads it through Jira’s API.

Contact your Jira administrator first. In Jira Cloud, also check the Atlassian status page .

”503 Error”

A 503 error usually means that Jira is temporarily down or under heavy load. Wait a few minutes and try again. If it persists, contact your internal help desk. In Jira Cloud, check the Atlassian status page .

”429 Too Many Requests”

Jira Cloud limits how many requests an app can send. Atlassian has enforced these rate limits for apps since 2 March 2026.

Wait a few minutes and try again. If the error occurs regularly, contact support and tell us the time (with time zone) when it happened.

”400 - A value with ID ‘xxxxx’ does not exist for the field ‘project’”

This error is most commonly caused by a space that you cannot access. Jira uses the technical name “project” for spaces in this message. The space can be selected in the Flower Settings, on a swimlane, or on a BPMN activity. The most common cause is that the space key was renamed, but access permissions may also have changed, or the space was deleted.

The same applies to the message for the field issuetype, which refers to a work type.

First, check the space selected in the Flower Settings. Then check the space and work type in your process model, on the activities and on the swimlanes, and make sure that you can access all of them.

For example, if your process model looks like this:

you need to check that you can load the AGILE space.

Why do I see a notice that Flower might stop working?

In Jira Cloud, Atlassian shows this notice for many Marketplace apps. It concerns a component of Atlassian’s platform, not Flower itself, and it does not affect Flower for Data Center.

Flower is Cloud Fortified, and we make sure that the app always meets Atlassian’s platform and security requirements. We will keep you informed about all relevant changes.

How to Raise a Support Request

How to Contact Flower

For support with Flower, you can raise a support request here.

Please share anything that helps us to solve your issue quickly:

Screenshots and a short description of what you did
Your Jira site (Cloud) or Jira version (Data Center) and the Flower version
The key of the process model and the process instance
The time when the problem occurred, with your time zone
A copy of your browser console (see below)

Atlassian Community

Ask a question on the Atlassian Community, a forum for all questions about Atlassian products. The Flower support team and power users monitor the Atlassian Community and respond promptly to usage questions.

Requests made via the Atlassian Community are answered on a best-effort basis.

Browser Console

Here’s how to get a copy of your browser console if we ask for it.

Chrome:

Open Developer Tools under More tools.
Select the Console tab.
Right-click in the console and select Save as…. Save the file and attach it to the support request.

In Firefox and Edge, open the developer tools with F12. The console works in the same way.

How to Raise a Feature Suggestion

Have an idea for our app? Send it to our product team via support. Click here to start a request.