Katalyst D2D
Frequently asked questions and solutions for Katalyst D2D
- Katalyst: Operation Parameters missing or not accepting Decimal Values
- Katalyst: Related Record Sets Must Be From Valid Versions to display editable parameter fields
- Katalyst: Safe Shutdown and Startup Procedure
- Katalyst: Scope is locked by other process
- Katalyst: Error when cloning experiments with existing KAT ID
- Katalyst: Configure and use CSV templates for material import
- Katalyst: “No experiments found” in Katalyst search – common causes and fixes
- Katalyst: Finalizing and Reopening Experiments Workflows
- Katalyst: Understanding when to use reaction vs analysis plates
- Katalyst: Resolving mismatched versions between Katalyst and Spectrus DB
- Katalyst: Experiment creation fails due to missing mandatory fields
- Katalyst: Sequence file missing for Katalyst experiment – impact and recovery options
- Katalyst: Managing duplicate compounds across plates and experiments
- Katalyst: Creating multiple (bulk) Katalyst experiments from plate templates
- Katalyst: General guidelines for multi-environment setups (dev/test/prod)
- Katalyst: “No materials found” error in Katalyst when importing from an external materials source
- Katalyst: users lose access to experiment after project ownership change
- Katalyst: Mismatch between reaction and analysis plate layouts
- Katalyst: Export from Katalyst to a downstream system fails due to invalid characters in names or IDs
- Katalyst: Experiment cannot be finalized due to missing analytical data
- Katalyst: User cannot see certain experiments due to missing role or group assignment
- Katalyst: Robot sequence files not recognized due to naming mismatch
- Katalyst: Experiment fails to open due to missing or corrupt attachments
- Katalyst: High-level checklist before performing a Katalyst upgrade
- Katalyst: Determining root cause of a Katalyst crash
- Katalyst: Performance problems after infrastructure changes
- Katalyst: Handling login issues after identity provider / SSO changes
- Katalyst: Handling 502 Proxy errors on RPC calls, general approach
- Katalyst: Workflow guidance to ensure peaks are correctly named
- Katalyst: Product peaks not assigned even though masses are known