Website Error: Something went wrong: Cannot resolve binding

I keep getting an error "Cannot resolve binding: returns.IRS1040.Return.ReturnData.IRS1040ScheduleC[UUID='ffd2eff1-0a9a-4f4d-a0b6-8c6edd5f246d'].ScheduleCWorksheet.SuppliesExpenses" and nothing I can do makes it go away. I've cleared the browser cache and cookies in Chromium, and even tried using a different browser (Firefox). Nothing I've tried makes this go away, and I can't delete the data in question either like I was able to when I ran into a similar issue last year (phone support ultimately suggested this after trying many things and nothing working).

 

 

 

 

FCI Failure

Object { msgProps: {…}, appProps: {…}, context: {…}, queued: false, flushLogsImmediately: false, destination: (2) […] }
​appProps: Object { userid: "[removed]", authid: "[removed]", pseudonymId: "1aaa9b6deff9d4ef09305ca431eb5a056", … }
​context: Object { appExpId: "turbotaxonline-app-experience", route: "/unified/2024/index/tto", url: "https://us-east-2.turbotaxonline.intuit.com/unified/2024/index/tto?uid=[removed]&version=145&fepath=%2Ffe%2Fty24usindprod&pyAmend=false&csrc=[phone number removed]&swimlane=useast2&alias=ty24usindprod&currentTaxYear=2024&locale=en_US", … }
​destination: Array [ "Intuit.shell.appfhostedshell", "Intuit.app.shell.ttouiappexperience" ]
​flushLogsImmediately: false
​msgProps: Object { ciName: "schedule-e-mcui-view.scheduleemetatopic.UpdateItem", ciOutcome: "failure", ciOutcomeReason: "Cannot resolve binding: returns.IRS1040.Return.ReturnData.IRS1040ScheduleC[UUID='ffd2eff1-0a9a-4f4d-a0b6-8c6edd5f246d'].ScheduleCWorksheet.SuppliesExpenses", … }
queued: false
<prototype>: Object { … }



Config: Invalid property

 

 

 

 

 

 

This is from the developer console. My screen shows:

 

"Hmm, looks like we hit a slight snag in this section

Let's get you back to your taxes. Make sure your Internet is connected, and then select Try again or check back in a few minutes."

 

I've tried again over the span of a few days and I'm not sure what to do. This looks like a bug in TurboTax itself, so I feel somewhat stuck. Can someone assist with a workaround?