Condition failed because one or more issues failed to index in time

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

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

Problem

Automation for JIRA showing "Condition failed because one or more issues failed to index in time" error when:-

  • Automation contains JQL search like below (without- Refetch issue data)

    (Auto-migrated image: description temporarily unavailable)
  • Issue 1 (Task Issue Type) had transited to Closed and Archived

  • Issue 2 (Task Issue Type) with In Progress had a Sub-Task Issue 2

  • Sub-Task Issue 2 transited to Closed triggered the automation to scan through entire instance using JQL query

  • Due to JIRA reindexing slowness issue, it triggers errors for Issue 1 Archived ticket

  • To replicate the issue again, we need to restore Issue 1 ticket and re-archive it

  • Then trigger another round automation by transit issue 2 subtask to done status

The following appears in the Automation for JIRA Audit Logs

1 Condition failed because one or more issues failed to index in time

Cause

JIRA couldn't finish reindexing on time before automation rules run or slow indexing.

Resolution

Include Re-fetch issue data before the JQL query run just like showing in the example screenshot.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.