[SOLVED] Invalid object return type

Bugs Solved Bugs
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…

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

Current behavior

In our application asap-hub we have a Usesr entity with an orcidWorks property that contains an array of nested entity. Among these there is a publicationDate field of type Json. The object it contains is:

{
    "year": "2020",
    "month": "09",
    "day": "08"
}

however for some reason the response from graphql for this field is:

"publicationDate": {
              "year": {
                "Type": 5
              },
              "month": {
                "Type": 5
              },
              "day": {
                "Type": 5
              }
            }

This applies to entire collection however (ie affects all records with this field populated) however the particular User entity in question has an ID 9fcd3a1d-951e-451d-8d12-00c2d1a19432

Expected behavior

The expected output should be (and used to until like an hour ago):

publicationDate: {
            year: '2020',
            month: '09',
            day: '08',
          },

Minimal reproduction of the problem

Try this query

query {
  findUsersContent(id:"9fcd3a1d-951e-451d-8d12-00c2d1a19432") {
    flatData {
      orcidWorks {
        publicationDate
      }
    }
  }
}

Environment

  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [x] Cloud version

Version: [VERSION]

Browser:

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

Others:

This is a production issue affecting our production systems and it is urgent

1 Like
2

@Sebastian would you be able to look into that? our production systems are impaired

3

I have rolled back and will have a look.

4

I have checked production and the problem seems to be fixed.

5

We are facing a new issue which started 6 minutes ago. We are investigating but thought it be worth sharing here as well.

Update
Squidex Cloud appears to be down :expressionless:

6

Not for me, it is up and running here.

7

TLDR New assets were broken during the rollback.

8

This topic was automatically closed after 2 days. New replies are no longer allowed.