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
- History not updating after content changes
- When content is updated, the history does not reflect the changes.
- There are no errors reported in the event consumers.
- Resetting all event consumers temporarily resolves the issue, but after some time the problem returns: history stops updating again.
- History functions not working (Load and Compare)
- The Load and Compare features in the history view are not functioning.
- They did work correctly when we first set up a fresh/clean instance with Docker, but stopped working afterward.
- Content update rules not triggered
- When the history is not updating, none of the content update rules are triggered either.
Expected behavior
- When content is updated, it should update the status history
- I should be able to Load previous versions and Compare in history
- Content rules should be triggered when the content is updated.
Minimal reproduction of the problem
- Update any content
- View in the history the updated status
Environment
App Name: dev, prod
- [ x ] Self hosted with docker
- Self hosted with IIS
- Self hosted with other version
- Cloud version
Version: [VERSION]
Browser:
- Chrome (desktop)
- Chrome (Android)
- Chrome (iOS)
- Firefox
- Safari (desktop)
- Safari (iOS)
- IE
- Edge
Others:
- Using MongoDB Atlas