Welcome @ezintlem597
Yes, the job may be exceeding resources at some point during the processing. We would usually suggest at least one rerun but it sounds like you have tried that already.
Checking the input data would be the next step. In particular, assembly is very sensitive to read format and quality. We have tutorials from the VGP project that go through some examples of data preparation, including QA assessments.
From there, we might be able to help more here. Would you like to generate a share link to your history and post that back in a reply for troubleshooting help? If you are using a workflow, you could instead post back the invocation share link, and that would provide more details about the upstream steps.
Let’s start there and please let us know if you solved this already! ![]()
Just so you know: Staying connected to your Galaxy account after a workflow is launched (or a job is the history is queued/executing!) is not needed since everything is happening on the server. It is only important to stay connected when loading data between your computer and the server, or when using certain visualizations that are communicating with your web browser. All other tasks happen on the server and you can come and go as it is convenient.