Thank you, that makes sense! We’re having some unrelated cluster issues currently, but I will try the workaround later today.
For the profile named “Tundra_110k_UseMe” the output is -
{"_id": "69c588ae26904d8502b810c5", "updated_at":
"2026-04-23T13:43:45.287000", "created_at": "2026-03-26T19:27:42.334000",
"title": "Tundra_110k_UseMe", "created_by_user_id":
"65a6d42b3cbefe33fcf5c15c", "last_applied_at": "2026-04-23T1
3:43:45.287000", "compute_resources": {"phase_one_lane": "dfci-cluster",
"phase_one_gpus": 2, "phase_two_lane": "dfci-cluster", "phase_two_gpus": 2,
"phase_two_ssd": true, "auxiliary_lane": "dfci-cluster", "auxiliary_gpus":
1, "auxiliar
y_ssd": true, "priority": 0, "phase_one_workers_per_gpu": 1}, "exp_groups":
[], "session_params": {"gainref_flip_x": false, "gainref_flip_y": false,
"gainref_rotate_num": 0, "psize_A": 1.2, "accel_kv": 100.0, "cs_mm": 1.6,
"total_dose_e
_per_A2": 30.0, "phase_plate": false, "neg_stain": false,
"eer_upsampfactor": 2, "eer_numfractions": 40, "motion_res_max_align": 5.0,
"bfactor": 500.0, "frame_start": 0, "output_fcrop_factor": 1.0,
"variable_dose": false, "smooth_lambda
_cal": 0.5, "optimize_for_gpu_memory": false, "output_f16": true,
"blob_diameter_min": 80.0, "blob_diameter_max": 150.0, "use_circle": true,
"use_ellipse": false, "use_ring": false, "blob_lowpass_res_template": 20.0,
"blob_lowpass_res":
20.0, "blob_min_distance": 1.0, "blob_max_num_hits": 4000,
"thresh_score_min": 0.3, "box_size_pix": 256, "extract_f16": true},
"run_configuration": {"exposure_processing_priority": "normal",
"phase_one_wait_for_exposures": false, "auto
_pause": "graceful", "auto_pause_after_idle_minutes": 30}}
I don’t think it’s related, but auto-pause also never triggers for this preset. We come in the next morning (often 12+ hours since the last exposure of a 1000 movie dataset) and it is still waiting.