Katalyst: Reprocessing not performed

Description
Reprocessing requests may fail to start or appear stuck when the connection to the ActiveMQ service is lost or when servers were started in an incorrect sequence. Refreshing the Katalyst page may resolve temporary issues, but persistent failures require checking service startup order and verifying ActiveMQ connectivity.

Solution

• Refresh the Katalyst web page. If reprocessing still does not start, proceed with the steps below.
• Verify ActiveMQ connections
  • Open the ActiveMQ administrator panel and ensure that the required connections are established.
  • If connections are missing, restart the Web Server again, following the correct startup order below.
• Restart the Web Server (in correct server startup order). It is essential that servers start in the following order:
  • Arcus Server
  • Oracle DB Server
  • Spectrus DB Server
  • MongoDB Server (if installed on a dedicated machine)
  • Automation Server
  • Web Server
• Check Automation Server processing log files:
  • Navigate to the Common Logs directory.
  • The path is defined in the CONFIG.INI file under:
    • CommonLogsDir
  • In the dated subfolder, open the log file associated with the relevant process and review it for errors.
  • Identify any explicit references to missing templates, instrument definitions, or processing parameters.
• The affected experiments were created with older versions of templates or instrument settings.
  • Confirm that:
    • The processing template referenced by the experiment still exists and is compatible with the current Katalyst version.
    • The instrument configuration (e.g., for LCMS untargeted analysis) is valid and mapped correctly in Spectrus DB.
  • Recommended approach:
    • Create a new processing template with the desired settings and save it.
    • In Katalyst’s Reprocess widget, explicitly select this new template for the experiment rather than relying on legacy references.
    • Run reprocessing again and verify the results.
  • If the experiment is tightly bound to an obsolete instrument configuration, clone the experiment or re‑import analytical data into a new experiment that uses the updated instrument setup.
    • Document the new template and instrument configuration as the standard for similar experiments going forward.
• Contact Customer Support for assistance.