I have the exact same issue. I have always used Turbotax but this is beyond frustrating to repeatedly get this error message. I spoke to one of their representatives who did a screen share with me, and I was told the system is overloaded and to try again later. I have tried all times of the day over the last week and it is still giving me the same error message. It's ridiculous.

@bfiander We are aware of this issue, and our development team is working on a resolution. We appreciate your patience.

Thanks.   Do you have any idea as to how long it will take to fix the issue?  It has been a month since I first experienced this error and have been checking periodically to see if it is fixed.    If there is a work around to paper file or another option?  We are expecting a refund so don't want to delay filing much longer.

Thanks @TurboTaxAniqua, I typed on another forum thread and saw this one, so looking forward to a response and resolution too

Hi Folks,

I tried copying the tax return (you can do this easily from the View all returns page, online version) and trying to submit with the COPY.   It worked for me.   Just thought I'd suggest this as it seems others are experiencing the same error.

@bfiander I tried to make a copy, and open the new file it created, but sadly I'm still getting the puppy error at URL  https://ww1.2024.ca.turbotaxonline.intuit.com/secure/yellowSticky

This should not have happened. Don't worry - your data has been saved.

Our TurboTax application has stopped working properly. It rarely happens; we're sorry it happened when you were using it.

Maybe the puppy helps, but you're probably mad and we're already hard at work fixing it.

Please check back again soon. We should resolve this quickly.

You can also contact our support team at https://support.turbotax.intuit.ca/contact/

Thanks for your patience,

The TurboTax Team

@bfiander We are aware of this issue, and our development team is working on a resolution. We appreciate your patience.

Didn't work for me and wasted one of my uses.

@kmcilmurray We are aware of this issue, and our development team is working on a resolution. We appreciate your patience.