Error message after migrate from v 4.4.0 to V7.0.1 (Blazor Server APP , Tired) #4611

We make a migration of our App from abp.io version 4.4.0 to version 7.0.1

• ABP Framework version: v7.0.1
• UI type: Blazor Server
• DB provider: EF Core / MongoDB
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace:
• We get this error message in the Auth logs and Host Log:
• 2023-02-13 11:41:01.959 -04:00 [ERR] value length must be equal to or lower than 65536! (Parameter 'value') System.ArgumentException: value length must be equal to or lower than 65536! (Parameter 'value') at Volo.Abp.Check.Length(String value, String parameterName, Int32 maxLength, Int32 minLength) at Volo.Abp.LanguageManagement.External.LocalizationTextRecord..ctor(Guid id, String resourceName, String cultureName, String value) at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.K2Xwd6Tvul(SaveContext , LocalizationResource , String , IStringLocalizer ) at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.K2Xwd6Tvul(SaveContext , LocalizationResource , String , IStringLocalizer ) at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.rJYwS5QxcO(SaveContext , LocalizationResource ) at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.SaveAsync() at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.SaveAsync() at Castle.DynamicProxy.AsyncInterceptorBase.ProceedAsynchronous(IInvocation invocation, IInvocationProceedInfo proceedInfo) at Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapter.ProceedAsync() at Volo.Abp.Uow.UnitOfWorkInterceptor.InterceptAsync(IAbpMethodInvocation invocation) at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter1.InterceptAsync(IInvocation invocation, IInvocationProceedInfo proceedInfo, Func3 proceed) at Volo.Abp.LanguageManagement.LanguageManagementDomainModule.<>c__DisplayClass6_1.dqYSTJLxrtjUOO4OmDO.MoveNext() --- End of stack trace from previous location --- at Polly.AsyncPolicy.<>c__DisplayClass40_0.<<ImplementationAsync>b__0>d.MoveNext() --- End of stack trace from previous location --- at Polly.Retry.AsyncRetryEngine.ImplementationAsync[TResult](Func3 action, Context context, CancellationToken cancellationToken, ExceptionPredicates shouldRetryExceptionPredicates, ResultPredicates1 shouldRetryResultPredicates, Func5 onRetryAsync, Int32 permittedRetryCount, IEnumerable1 sleepDurationsEnumerable, Func`4 sleepDurationProvider, Boolean continueOnCapturedContext)

2023-02-13 11:41:23.039 -04:00 [ERR] value length must be equal to or lower than 65536! (Parameter 'value') System.ArgumentException: value length must be equal to or lower than 65536! (Parameter 'value') at Volo.Abp.Check.Length(String value, String parameterName, Int32 maxLength, Int32 minLength) at Volo.Abp.LanguageManagement.External.LocalizationTextRecord..ctor(Guid id, String resourceName, String cultureName, String value) at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.K2Xwd6Tvul(SaveContext , LocalizationResource , String , IStringLocalizer ) at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.K2Xwd6Tvul(SaveContext , LocalizationResource , String , IStringLocalizer ) at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.rJYwS5QxcO(SaveContext , LocalizationResource ) at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.SaveAsync() at Volo.Abp.LanguageManagement.External.ExternalLocalizationSaver.SaveAsync() at Castle.DynamicProxy.AsyncInterceptorBase.ProceedAsynchronous(IInvocation invocation, IInvocationProceedInfo proceedInfo) at Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapter.ProceedAsync() at Volo.Abp.Uow.UnitOfWorkInterceptor.InterceptAsync(IAbpMethodInvocation invocation) at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter1.InterceptAsync(IInvocation invocation, IInvocationProceedInfo proceedInfo, Func3 proceed) at Volo.Abp.LanguageManagement.LanguageManagementDomainModule.<>c__DisplayClass6_1.dqYSTJLxrtjUOO4OmDO.MoveNext()

• Steps to reproduce the issue:"
• Make a migration with EF, run migrator after that we get that error frecuently on app exectution.