Thanks for catching that. It's amazing how many times we've made a change elsewhere in the program that has broken timing imports. This one broke when I added the support for choosing the different sequence timings (25ms, 50ms, and 100ms). I was trying to read the sequence timing from a variable that wasn't set yet. Before adding that support the variable was hard coded so it always worked but was hard coded to snap the timings to 25ms. Now it will snap the timings to whatever is the chosen sequence timing.
I also discovered we had a crash when importing the same file twice so I made it keep appending "_1" to the name until it finds an unused name.