Katalyst: Scope is locked by other process

When generating an EDBO scope in Katalyst, you may receive a message indicating that the scope is locked by another process. This typically occurs when a previously submitted scope generation request is still being processed by the Bayesian Optimizer Server (BOS).

Large scopes, particularly those with a high number of one-time reactions, can require significant processing time. While a scope is being generated, additional scope generation requests may be blocked until the initial task has completed.

To resolve this issue:

1. Verify whether a scope generation process is already running by reviewing the Katalyst web server and BOS logs.
2. Avoid submitting multiple scope generation requests for the same project while a previous request is still in progress.
3. Allow the current scope generation task to complete before attempting to generate another scope.
4. If scope generation is taking an excessive amount of time, consider reducing the scope complexity, such as lowering the number of one-time reactions, and then retry the operation.

Note: Generation time depends on the size of the scope and the available hardware resources. Large scopes may take several hours to complete.

Additional Troubleshooting

If the issue persists, collect the following logs for further investigation:

• Katalyst/Tomcat logs (entire log folder)
• The last 2,500 lines of the BOS log
• Relevant SDBES logs:
  • cbookserver_errors.log
  • cbookreindexer_errors.log
  • cbookserver_scripts.log

These logs can help identify whether the scope is actively processing or if another issue is preventing completion.