@Joely_Corrales, This is resulting from a bug that has been fixed for the 2026.1 release. See this discussion. The best workaround I have right now would be to install 2025.7 and work with that for this step - if you're stuck we may be able to help with another option when we're all back in the office the week of Jan 5.
Sorry for the trouble!