Complete List of Jira Agile LexoRank Errors and Fixes

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

This page is a compilation of all known Lexorank errors that come from the JIRA Software source code. We have also tried to explain the problem that causes the error to be thrown, as well as the action plan to fix it.

See also another page: Troubleshooting LexoRank System Issues

Solution

Description

List of all known Agile Lexorank Errors with the brief Problem description and related possible Action.

Rebalancing errors

Error

Problem

Action

Expected the row to migrate to be in the old bucket [oldBucket=%s, rowBucket=%s]

OR

Expected the row last migrated to be in the new bucket [newBucket=%s, rowBucket=%s]

Value of "Bucket in RANK" doesn't match the value of "BUCKET column" for a specific row

Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed, please follow steps from Share_Logs_Data (see Actions section below)

see article : Lexorank Rebalancing gets stuck with Error "Expected the row last migrated to be in the new bucket"

Couldn't find rows on balance boundary

JIRA couldn't find 2 rows balance boundary during balancing.

Data in AO_60DB71_LEXORANK table needs to be reviewed, please follow steps from Share_Logs_Data (see Actions section below)

Failed to save rank row, retry

Each individual ranking operation has 1500 ms timeout for rank lock. JIRA couldn't save migrated data into DB and will retry.

In most cases problem caused by slow DB.

Check DB performance, see possibly related

JSWSERVER-16542

Failed to save rank row, aborting

JIRA couldn't save migrated data into DB and stopped. Problem is not clear.

Please follow steps from Share_Logs (see Actions section below)

Rank Errors

Error

Problem

Action

WARN [c.a.g.customfield.lexorank.LexoRankCFType] Unable to retrieve rank for field [10600] and issue [2341873] WARN [c.a.g.customfield.lexorank.LexoRankCFType] gh.api.rank.error.lexorank.fieldlength.exceeded.norebalance

Future allocated RANK length for issue [2341873] exceeds 254 characters during ranking operation, that operation will not be possible until RANK length gets back to normal.

The problem should be fixed by rebalancing.

Check if rebalancing is running, wait until it's finished

If the problem persists, please follow steps from Share_Logs (see Actions section below)

See also: Jira Software throws UI error when ranking issues on boards

com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly one rank row for issue[id=%d] for rank field[id=%d], but found %d rows

There are multiple RANK rows for the same Field with sameIssueID

Data in AO_60DB71_LEXORANK table is duplicated and needs to be fixed

See articles :

LexoRankIntegrityException: Expected exactly one rank row for issue x for rank field y, but found 2 rows

IndexingFailureException thrown during reindex of Jira server

com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly one minimum marker row for rank field[id=%d], but found %d

or similar:

Expected exactly one maximum marker row forrankfield[id=%d], but found %d

Correspondingly:

There more than one "Minimum marker row" (?|000000).

There more than one "Maximum marker row" (?|zzzzzz).

Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed

Please follow steps from Share_Logs_Data (see Actions section below)

com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected the rank row to be of type %s. Found row[%s]

Problem with "Minimum marker row" (?|000000). Either:

- it's not present

- it's not in the first position ORDER BY ASC

Problem with "Maximum marker row" (?|zzzzzz). Either:

- it's not present

- it's not in the first position ORDER BY DESC

Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed

See:

LexoRank Integrity Check fails with rank out of bounds error in Jira server

- If the problem persists, please follow the steps from Share_Logs_Data

com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected to find minimum marker row for rank field[id=11960], but found none.

or similar:

Expected to find maximum marker row forrank field[id=%d], but found none.

Correspondingly:

- There is no "Minimum marker row" (?|000000).

- There is no "Maximum marker row" (?|zzzzzz).

- Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed

- Or stale balancing job - Jira server throws LexoRankIntegrityException error during reindexing or reranking operations

- If the problem persists, please follow steps from Share_Logs_Data (see Actions section below)

com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly 2 rows; the minimum marker row and the highest ranked row forrank field[id=%d]

or similar:

Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=%d]

JIRA couldn't find 2 row in last/first position ORDER BY ASC.

Problem is not clear.

Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed

See article : Reindexing fails with expected exactly 2 rows error in Jira server

com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected the first rank row to be of type %s. Found row[%s]

Problem with "Minimum marker row" (?|000000). Either:

- it's not present

- it's not in the first position ORDER BY ASC

Problem with "Maximum marker row" (?|zzzzzz). Either:

- it's not present

- it's not in the first position ORDER BY DESC

Data in AO_60DB71_LEXORANK table is corrupted and needs to be fixed

Please follow steps from Share_Logs_Data (see Actions section below)

Enable Additional Logging for LexoRank

By default, the logging of ranking system is disabled. To get detailed logging of what the system is doing add a new logger to JIRA's Logging and Profiling page

  1. Logging for balancing

    level: DEBUGpackage: com.atlassian.greenhopper.service.lexorank.balance

  2. Logging for ranking

    level: DEBUGpackage: com.atlassian.greenhopper.service.lexorank

  3. Logging for ranking DB operations

    level: DEBUG package:

    com.atlassian.greenhopper.manager.lexorank

  4. Logging for statistics:

    every minute logs the activity and performance of the ranking system level: DEBUG package: com.atlassian.greenhopper.service.lexorank.LexoRankStatisticsAgent

Actions

Action

Steps

Share_Logs

Please do the following steps:

- Enable DEBUG logging and reproduce the problem (see Enable Additional Logging for LexoRank section)

- Generate JIRA support zip.

- and contact Support

Share_Logs_Data

Please do the following steps:

- enable DEBUG logging and reproduce the problem (see Enable Additional Logging for LexoRank section)

- Generate JIRA support zip.

- please provide us with the result of the following SQL (preferably in a CSV file format).

SELECT * FROM "AO_60DB71_LEXORANK" ORDER BY "RANK"

- and contact Support

Updated on June 2, 2025

Still need help?

The Atlassian Community is here for you.