@mesquitebean,
Thank you for the quick response.
I think this thread was discussing about 48 hour hold before efiling, not after efiling. I understand the compromised account scenario.
Related link from the post - https://ttlc.intuit.com/community/security/help/i-received-an-email-about-a-return-with-my-informati...
Normally , in the past i have filed in the weekends. In this case of a 48 hour hold expiring in the weekend , the expectation was Turbotax "should have" attempted to file automatically as per their 48 hour hold email. Or at least after 10 hours of crossing the 48 hour mark. if that had happened and sent confirmation through email or text that it was automatically efiled and waiting for confirmation from IRS, then it would have calmed my nerves. However that did not happen.
Hence the question of how the 48 hour was calculated (whether consecutively from the time it was placed on hold or whether it was 48 hours of business days).
Also when the hold is in place, if you try to file through turbo tax , the turbo tax error message was - ""We had a problem while saving your return for filing. Please try to e-file again and if that fails contact customer service."
If the error message was phrased something like " Your account is currently on hold. Please try agian later" or "Your account is currently disabled from filing due to security reasons, please contact customer service" , that would have helped to understand that account is still in the lockdown phase.
I had called their customer service again but turbotax support is not able to confirm whether the account is still on hold. They suggested to wait it out till 72 hours or the next working day call back to check again.
Frustrating part is that not knowing whether the error is due to the 48 hour hold or something else. Have to wait for that period to pass before knowing further.
Additionally the internal turbotax maneuver does not seem to be automated. One would think upon receiving the 48 hour hold email specifying to call back to confirm if it is really you or some one else, and you call back immediately after the email and specify it is indeed you from a different account, you would expect the hold to lapse immediately upon user confirmation or by the said 48 hours or few hours after the 48 hours, since that did not happen even after 62 hours, i am guessing that it is either not automated or is not automated to continue in weekends (may be a batch process that triggers during weekdays).
I will wait and see if that changes in a day or so...
Normally online applications will have -
1) some kind of error message to error code mapping that can help their customer support identify root cause of error message (if not the exact root cause, some where close to the path of debugging the root cause)
or
2)some kind of logging system like splunk or kibana or even raw logs that record the errors encountered in web applications. when you cobrowse the problem with the customer and reproduce the errors, they can connect with their iT to determine what is failing by parsing the logs quickly.
Was disappointed they were not able to help troubleshoot that way.
I will reply back if it gets resolved later.
