Hey everyone, I've been upgrading an Umbraco 8 site to Umbraco 13 following the standard upgrade path: v8 → v10 v10 → v13 Everything seemed to work fine after migrating the code from .NET Framework to .NET Core, and the site runs and loads as expected. However, I'm running into an issue with Umbraco Forms—specifically, they are not submitting correctly. When trying to submit a form, I get the following error:

InvalidOperationException: No UmbracoRouteValues feature was found in the HttpContext

    Umbraco.Cms.Web.Website.Controllers.SurfaceController.get_CurrentPage()
    Umbraco.Forms.Web.Controllers.UmbracoFormsController.ApplyUmbracoPageId(Record record)
    Umbraco.Forms.Web.Controllers.UmbracoFormsController.SubmitForm(Form form, FormViewModel model, IDictionary<Guid, string> formFieldValuesForConditions, IDictionary<string, string> additionalData)
    Umbraco.Forms.Web.Controllers.UmbracoFormsController.UpdateFormStep(Form form, FormViewModel model, IDictionary<Guid, string> formFieldValuesForConditions, IDictionary<string, string> additionalData, int direction)
    Umbraco.Forms.Web.Controllers.UmbracoFormsController.GoForward(Form form, FormViewModel model, IDictionary<Guid, string> formFieldValues, IDictionary<string, string> additionalData)
    Umbraco.Forms.Web.Controllers.UmbracoFormsController.HandleForm(FormViewModel model)

Steps Taken So Far: + Verified that Umbraco Forms is installed and running. + Checked all necessary migrations were applied during the upgrade. + Ensured forms are being rendered correctly in views. Has anyone encountered this issue before when upgrading? Any insights or troubleshooting tips would be greatly appreciated! Thanks in advance! 🙌

Verifying: have you upgraded Umbraco Forms to the latest v13 supported version?

Yes!

lack of UmbracoRouteValues means something is wrong with umrbaco routing, are you using umbraco routing or custom routing? if you using custom routing you might want to add required values by hand 🤔

I will give that a try to see. On this site there is no custom routing which is why this error is so odd.