Content is not updating for "Components" reference field with multiple items

Support
1

I have…

  • [x] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

I have created a schema (Single content) and added components field (with four text fields and one assets field) to add items in an array, for first two items it successfully updates the content but when I add third one it throws error “Failed to update content. Please reload.” and “Failed to load resource: the server responded with a status of 502” in console

Expected behavior

It should update content with more than two items

Environment

  • [x] Self hosted with Google Kubernetes engine
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: [6.8.0]

Browser:

  • [x] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:

this is the output in console

image
image1662×33 8.11 KB

2

Afaik 502 is nothing from Squidex: https://success.outsystems.com/Support/Troubleshooting/Application_runtime/Troubleshooting_HTTP_502_bad_gateway

What do you use as an ingress or load balancer? You should check the logs.

3

Thank you for your response.
We are using ingress and I have checked the logs, this is what I am getting in logs

Exception type: System.TimeoutException
“message”: “Response did not arrive on time in 00:00:30 for message: Request S127.0.0.1:11111:396565635*cli/7750379f@62bd0599-\u003ES127.0.0.1:11111:396565635*grn/Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain/0\u002B05f18c1c-9ae5-4f90-873c-29d427f96a07--67b315a8-8976-45ec-880e-e26c0123f35f@6d0160ad InvokeMethodRequest Squidex.Domain.Apps.Entities.Contents.DomainObject.IContentGrain:ExecuteAsync #314266. Last known status is IsExecuting: False, IsWaiting: True, Diagnostics: [[Activation: S127.0.0.1:11111:396565635*grn/Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain/0\u002B05f18c1c-9ae5-4f90-873c-29d427f96a07--67b315a8-8976-45ec-880e-e26c0123f35f-0x4DA69EED@6d0160ad #GrainType=Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain Placement=RandomPlacement State=Valid NonReentrancyQueueSize=3 EnqueuedOnDispatcher=0 InFlightCount=1 NumRunning=1 IdlenessTimeSpan=01:13:59.4230651 CollectionAgeLimit=02:00:00], TaskScheduler status: WorkItemGroup:Name=[Activation: S127.0.0.1:11111:396565635*grn/Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain/0\u002B05f18c1c-9ae5-4f90-873c-29d427f96a07--67b315a8-8976-45ec-880e-e26c0123f35f@6d0160ad #GrainType=Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain Placement=RandomPlacement State=Valid],WorkGroupStatus=Waiting. Currently QueuedWorkItems=0; Total Enqueued=76; Total processed=76; Quantum expirations=0; TaskRunner=ActivationTaskScheduler-187:Queued=0; Detailed context=\u003C[Activation: S127.0.0.1:11111:396565635*grn/Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain/0\u002B05f18c1c-9ae5-4f90-873c-29d427f96a07--67b315a8-8976-45ec-880e-e26c0123f35f-0x4DA69EED@6d0160ad #GrainType=Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain Placement=RandomPlacement State=Valid NonReentrancyQueueSize=3 EnqueuedOnDispatcher=0 InFlightCount=1 NumRunning=1 IdlenessTimeSpan=01:13:59.4230734 CollectionAgeLimit=02:00:00 CurrentlyExecuting=Request S127.0.0.1:11111:396565635*cli/7750379f@62bd0599-\u003ES127.0.0.1:11111:396565635*grn/Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain/0\u002B05f18c1c-9ae5-4f90-873c-29d427f96a07--67b315a8-8976-45ec-880e-e26c0123f35f@6d0160ad InvokeMethodRequest Squidex.Domain.Apps.Entities.Contents.DomainObject.IContentGrain:ExecuteAsync #287768]\u003E, Message Request S127.0.0.1:11111:396565635*cli/7750379f@62bd0599-\u003ES127.0.0.1:11111:396565635*grn/Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain/0\u002B05f18c1c-9ae5-4f90-873c-29d427f96a07--67b315a8-8976-45ec-880e-e26c0123f35f@6d0160ad InvokeMethodRequest Squidex.Domain.Apps.Entities.Contents.DomainObject.IContentGrain:ExecuteAsync #287768 was has been executing for 01:13:46.0736093., Message Request S127.0.0.1:11111:396565635*cli/7750379f@62bd0599-\u003ES127.0.0.1:11111:396565635*grn/Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain/0\u002B05f18c1c-9ae5-4f90-873c-29d427f96a07--67b315a8-8976-45ec-880e-e26c0123f35f@6d0160ad InvokeMethodRequest Squidex.Domain.Apps.Entities.Contents.DomainObject.IContentGrain:ExecuteAsync #314266 has been enqueued on the target grain for 00:00:30.3902860 and is currently position 3 in queue for processing.]. Target History is: \u003CS127.0.0.1:11111:396565635:*grn/Squidex.Domain.Apps.Entities.Contents.DomainObject.ContentDomainObjectGrain/0\u002B05f18c1c-9ae5-4f90-873c-29d427f96a07--67b315a8-8976-45ec-880e-e26c0123f35f:@6d0160ad\u003E.”
4

Can you try to make an upgrade?. I think I know what the problem is.

5

We upgraded version from 6.8 to 7.0 but that resulted in all the content and schema disappearing from the apps. Also when when we tried restoring back ups that we took before up-gradation, the restoration didn’t worked as well.

6

7.0 is still on RC and not meant for production. I mean 6.9 or 6.10.

7

Sure, I will try with 6.10 and will keep you posted.
Thanks

1 Like
8

Hi @Sebastian,
Thank you so much :clap:, After upgrading to 6.10 everything is working properly.

1 Like