Tips and Troubleshooting
Overview
This guide focuses on troubleshooting issues specifically related to the BRC Analytics to Galaxy handoff and common reasons why a Galaxy workflow launched from BRC Analytics might fail.
New to Galaxy? If you are new to the Galaxy platform, please visit the Using Galaxy page first to learn about the interface, datasets, and where to find tutorials.
Data Management Tips
Organizing Your Galaxy Histories
- When you land in Galaxy, Create separate histories for different projects or experiments
- Name histories descriptively (e.g., "Measles_Surveillance_2024")
- Add tags to datasets for easy filtering
- Delete unnecessary files to manage storage (contact Galaxy support if you need a quota increase)
- Use collections to group datasets. Note: If you upload your own reads, you must typically organize them into a "Collection" (e.g., a Paired List) for BRC workflows to recognize and process them correctly.
Saving and Exporting Data
- Download results by clicking the download icon on any dataset
- Export workflows for reproducibility
- Share histories with collaborators via Galaxy's sharing features
- Publish analyses to make them publicly accessible
Troubleshooting Common Issues
When launching from BRC Analytics
- "Nothing is happening": After clicking Launch, it may look like the workflow is idle. Usually, this means Galaxy is downloading large datasets (like reference genomes or SRA reads). Check the history panel—if datasets are grey or yellow, the process is active.
- Not logged into UseGalaxy.org: If the handoff redirects you to a login screen, sign in and then relaunch the workflow from BRC Analytics so the configuration is sent with your authenticated session.
- Jobs appear in a different history: Galaxy runs workflows in whichever history was most recently active. Open the history panel and switch to the newest history to review datasets.
Analysis Failed (Red Dataset)
- Click on the red dataset
- Review the error message
- Common causes:
- Incompatible Input Data: While BRC filters inputs to match workflows (e.g., enforcing paired-end reads for paired-end workflows), users can manually override these filters when selecting SRA runs. If you force single-end data into a paired-end workflow, it will fail.
- Missing Galaxy Configuration: Some workflows have runtime parameters that must be set inside Galaxy after launch. If these are left as defaults, the tool may fail.
- Resource limits: Extremely large datasets might exceed default memory or time allocations.
- Adjust settings and re-run
Dataset Stuck in Gray/Yellow
- Jobs are queued - be patient
- Check the Galaxy status page for system issues
- If stuck >24 hours, report to support
Can't Find My Data
- Check you're viewing the correct history
- Use the search function in the history panel
- Datasets may be hidden - click "Include hidden datasets"
Best Practices
For Reproducible Research
- Document parameters: Note all settings used
- Extract workflows: Save your analysis pipeline
- Record provenance: Galaxy automatically tracks this
- Share complete histories: Include all inputs and parameters
- Publish workflows: Make methods available to others
For Efficient Analysis
- Start small: Test with a subset of data
- Use collections: Process multiple samples together
- Delete intermediate files: Keep only essential outputs
- Monitor job status: Check for errors early
- Save important results: Download completed analyses