The history section does not show the latest content updates

Support
1

I have…

  • Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
  • Used code blocks with ``` to format my code examples like JSON or logs properly.

I’m submitting a…

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

Current behavior

The latest content updates are not appearing in the history section, despite being successfully saved and published. Updates older than two days are displayed correctly, but only the most recent changes are missing.

UAT content item for reference

image
image1876×877 111 KB

Production content item

image
image1813×953 100 KB

Expected behavior

The history section should display all changes made to the content item, allowing for comparison and identification of the list of changes.

Minimal reproduction of the problem

  1. Open the details page of any content item
  2. Create a new draft
  3. Make content updates and save
  4. Publish the draft version
  5. Check history section

Environment

App Name: cargocrew-prod and cargocrew-uat3

  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: Latest

Browser:

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

Others:

2

We’re experiencing the same issue. Coupled with this, the rules are not being executed as well, which I think is stemming from the same problem.

Edit: We’re on Cloud version as well.

3

Same for me; rules are not being executed since yesterday.

4

Sorry, I have not realized that was coming back. I will investigate the problem again.

5

BTW, regarding the Rules with Algolia, last time when I tested deleting a content item, I did not need to put anything in the “Deletion” field for the rule in order for Algolia to remove the item from the index. I think this is a bug. Please let me know if you want me to create a new topic for this. But I thought I would metioned it since you’re going to have a look at the Rules feature.

6

I think the history and rules are solved now. Not sure what happens but somehow the “worker” became a normal node and was also service http requests.

7

History seems to be working again. However rules are stuck on Pending. Not sure if there’s a backlog that needs to be processed.

8

Rules seem to be working.

image
image1312×1154 99.7 KB

9

Yes, probably. Give it some time.

10

Rules have been executed successfully. Thanks for looking into it.

1 Like