we encoutered a crash due to a corruption in FCCS. Added error handling for that scenario which included a crashed list and modifying the export function. Need to test it on a known crashed folder

README.md

@@ -58,6 +58,7 @@ Requires FCCS to be open with export destination already configured. Automates t
 - **Resumable** -- tracks completed drawers in `completed.txt`; safe to restart
 - **Screenshots** -- captures failure states for diagnosis
 - **Defensive** -- one bad drawer won't crash the entire run
+- **Crash recovery** -- some documents (e.g. UltraTax "Diagnostics" files) crash FCCS's converter (`FileConversionEngine::convert() failed`), which aborts that drawer's export. The script detects the error dialog, screenshots and logs the crashing document, dismisses it, and records the drawer in `crashed.txt` so it's skipped on future runs instead of stalling. Handle crashed drawers manually (export them excluding the poison document); delete a line from `crashed.txt` to retry after fixing.
 
 ### Step 2b (optional): Verify Export Completeness
 
@@ -99,6 +100,6 @@ Exported filenames follow the format `{drawer_id}_{client_name}_{folder_name}_{c
 
 All scripts read from `config.ini` (or specify `--config path\to\config.ini`).
 
-- **`[paths]`** -- backup_dir, export_dir, output_dir, drawer_id_file, completed_file, ignore_file, log_file, screenshot_dir, manifest_dir, folder_list
+- **`[paths]`** -- backup_dir, export_dir, output_dir, drawer_id_file, completed_file, ignore_file, crashed_file, log_file, screenshot_dir, manifest_dir, folder_list
 - **`[timeouts]`** -- nav_timeout, dialog_timeout, progress_appear, progress_finish, settle, confirm_timeout
 - **`[controls]`** -- FCCS window class names and button titles (rarely need changing)