JQL not finding labels I made recently. How to force it to re-index?

[jake]

I have two labels, call them 'EarlierLabel' and a recently-created label called TestLabel1.  I added TestLabel1 to a ticket then tested JQL and was pretty dismayed to find that the ticket did not show up.   But when I tried out the JQL against other labels like the'EarlierLabel' one that existed already it worked.  This suggests that JQL does not reliably produce the most up-to-date results.  According to ChatGPT (and I know to take this with a grain of salt):

> Indexing Delay: Jira relies on indexed data for fast search results through JQL. Sometimes, especially in larger instances or instances with a lot of activity, there can be a delay between when an issue is updated and when that update is reflected in the search index. This might be what's causing the new tags to not show up immediately in JQL results.

Is this true, and is there a way to avoid having this issue of tickets not showing up in query results?  

[Mohanraj Thangamuthu]

Hello, Good day. If you try to add this label again on a new issue the label is shown or you getting option to create new label ?. My request is to create a label on issue1 and try to add this new label on issue 2. This is Jira cloud instance ?

[jake]

If you try to add this label again on a new issue the label is shown or you getting option to create new label 

As of yesterday at 11pm CT it was not showing up.  As of today at 1:45pm CT, the label is now showing up when I attempt to add it to a new ticket.  However, even now, the JQL query 

labels = TestTag1 ORDER BY created DESC

is returning no results still (even though I can confirm in UI that I have tickets in my project with this label.  I can even fetch the tickets using the Python

endpoint = BASE_URL + 'issue/MY_PROJECT-11696'
response = requests.get(endpoint, auth=AUTH)

and I successfully obtain the issue details including the labels with TestTag1.  But if I use JQL with the Jira API, same result: ticket not found by labels.  

Moreover, the issue does not seem to be with using a new label but rather querying a new association of a label to a ticket.  That is, if I repeat this experiment adding an existing label to an existing ticket, that association does not immediately reflect in my JQL response.   That is, using JQL to search for tickets with that label does not reflect the ticket I just added the label to.  

What are the SLA's of your DB?  How long can I expect it to take for the JQL server to update, because this is really annoying for doing project management.

[jake]

Yes we have our own Jira Cloud Instance.  

[Mohanraj Thangamuthu]

Hello, thanks for the response. I am unable to reproduce this behaviour on my instance. I would request you to create a support request so that our team could check further. https://support.atlassian.com/contact/#/