Welcome to the Alteryx Knowledge Base

Checklist Manual Re-index
user

Created/Edited - 4/30/2026 by Michael Adler | Alteryx

Procedure
UNDERSTAND THE ISSUE
Gather Alteryx Server version
 

 

Which part of the Server UI is affected by the stale index?
Alteryx Server has the following areas that the stale index can affect. In later Server versions,
some of the Lucene indexes have been removed. Find below the latest Server version that has the Lucene index
for the given Gallery Area.
 
Gallery AreaServer Version
Data Connections (Admin UI)Current
District (User and Admin UI)Current
InsightsCurrent
MediaCurrent
PageCurrent
Subscriptions (Studios)Current
TagsCurrent
UsersTill 2023.1
Workflows (Admin UI)Till 2023.1
Workflows (User UI)Current

 

EXCLUDE COMMON, SIMILARLY LOOKING ISSUES
Exclude issues with similar symptoms by reviewing Gallery logs.Review the appropriate KB. Check the Gallery logs for any errors mentioned in the KB
 

If the issues don't apply, continue below.

Exclude a failed MongoDB schema migration.Check that the Gallery logs contain the lines "Queue worker sleeping for 1 seconds..."

 

If the pattern above doesn't appear in the Gallery logs, you might face the issue described in the checklist on troubleshooting a failed MongoDB schema migration.

If the issue doesn't apply, continue below.

DECIDE WHICH RE-INDEX METHOD TO USE
Decide which re-index method to use
In most cases, use the manual re-index workflow / analytic app. It is contained in the KB article below.
Use it unless:
  • Using a MongoDB Atlas Database or a TLS-enabled user managed, MongoDB.
  • Preference for Command Prompt method
  • Gallery API cannot be used because of network restrictions, for instance because of a reverse proxy or a load balancer.
 
KB articles:
Follow the steps below in the relevant section.
RUNNING THE MANUAL RE-INDEX WORKFLOW METHOD (A)
Pre-Work
  • Collect the Controller token,
  • Get the host information for MongoDB.
  • For the workflow, Rebuild Gallery Indexes legacy.yxmd, additionally the MongoDB password (not Admin) is required.
For the User Managed MongoDB, please refer to the full article for details.
Run the manual re-index as an Analytic App.
  • Run the manual re-index workflow / analytic app. It is important to run it when there is little or no Gallery activity.
  • The steps for running it are included in the analytic app / workflow.
Confirm that indexing issue resolved
Confirm that symptoms of the "stale index" have been resolved in the Server UI.

The output file should look like the below for success.

 

For the legacy workflow, you will see the following or similar in the Results window - look for 200 OK in the DownloadHeaders.
The exact list of Collections depends on the Alteryx Server version.

   
RUNNING THE MANUAL RE-INDEX COMMAND PROMPT METHOD (B)
Pre-Work
  • Collect the MongoDB password (not Admin).
  • Get the host information for MongoDB.
Run the re-index via Command Prompt
  • Open an Admin Command Prompt and navigate to the Alteryx Server bin folder.
  • Run the appropriate command. Use the password from the pre-work.
    • For 2020.1 and later:
AlteryxServerHost.exe --rebuild -mongoconnection:mongodb://user:{PASSWORD}@localhost:27018/AlteryxGallery?connectTimeoutMS=25000 -luceneconnection:mongodb://user:{PASSWORD}@localhost:27018/AlteryxGallery_Lucene?connectTimeoutMS=25000 -searchProvider:Lucene
  • For 2019.4 and earlier:
AlteryxCloudCmd.exe --rebuild -mongoconnection:mongodb://user:{PASSWORD}@localhost:27018/AlteryxGallery?connectTimeoutMS=25000 -luceneconnection:mongodb://user:{PASSWORD}@localhost:27018/AlteryxGallery_Lucene?connectTimeoutMS=25000 -searchProvider:Lucene
There is no need to restart the AlteryxService.
Confirm that indexing issue resolved
The message "waiting for rebuild task to be claimed" should show in the Command Prompt.
Confirm that symptoms of the "stale index" have been resolved in the Server UI.
(OPTIONAL) TROUBLESHOOTING THE MANUAL REINDEX
Check that
 
 
 
 



 

Additional Information
Was this article helpful?