Matt Bookman

I just want to be clear on the original request; I'm unclear how we landed on the `print-config` command. I'm not opposed to it, but it wasn't the original request....

Hey @rivershah! I agree, that does look like a server-side error and retry. Batch documentation indicates that retries are configurable: https://cloud.google.com/batch/docs/automate-task-retries You can configure automatic task retries for each task...

Looks like the timeout flag value needs to be wired through to the TaskSpec as described here: https://cloud.google.com/batch/docs/set-timeouts#set-task-timeout `build_task_spec` is here: https://github.com/DataBiosphere/dsub/blob/dba9b8635e78036a9c6c1826e4c3ba31a280f1b5/dsub/providers/google_batch_operations.py#L126 and is called from here: https://github.com/DataBiosphere/dsub/blob/dba9b8635e78036a9c6c1826e4c3ba31a280f1b5/dsub/providers/google_batch.py#L802

Hi @StephanieArteaga ! This is a good question. `dsub` does not have built-in memory utilization insights, but there may be a few options. What I have done in the past...