Issue with "Insert Indel Qualities" Step in Galaxy Training Material after recent upgrade

Description:
While using the Galaxy NGS Data Logistics training material in a classroom setting, students encountered issues when processing a collection containing the datasets SRR12733957 and SRR11954102. These issues appear to have arisen after a recent upgrade to the Galaxy platform. Prior to the upgrade, the same training workflow and datasets (SRR12733957 and SRR11954102) were processed successfully without encountering the described problems.

Observed Behavior:

  1. For SRR12733957, the step Insert Indel Qualities remains stuck in a green “queued” state and does not proceed to execution.

    → As a result, the downstream step Call Variants fails due to missing input.
  2. For SRR11954102, although the Call Variants on collection 40 step completes and is marked as green, the resulting dataset contains 0 lines and 0 columns, indicating no output was generated.

Expected Behavior:

  • Both datasets in the collection should complete the Insert Indel Qualities and Call Variants steps successfully.
  • The final output should include variant call results with actual content, not empty tables.

Impact:
These issues prevent students from completing the training exercise and undermine the learning objectives of the tutorial.

History Link for Reference:

The previous issue seems to be resolved — thank you! However, there is now still a new problem: when running the SnpEff step on the same datasets (SRR12733957 and SRR11954102), the job finishes successfully (green), but the output is empty — 0 lines and 0 columns. This did not happen before the platform upgrade.

Hi @TEr_LeE

I’m glad you were able to notice the correction to the dataset metadata issues. There was also a problem with certain job containers (resolved just this week). You happened to run into both.

All of this should be resolved now across tools and datatypes. Our apologies about the bumpy release cycle this time. Our testing team is aware of what went wrong and is building in strategies to avoid a repeat.

Thank you for reporting the issue! If you notice any ongoing issues, we can follow up here or you can start again in a new topic. :slight_smile: