I have…
- [x ] 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
- [ x] Performance issue
- Documentation issue or request
Current behavior
Expected behavior
Minimal reproduction of the problem
Environment
App Name:
- [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:
I am Gayatri Landage, developer from Brightmine (XpertHR).
Over the past few days, we have observed a high volume of messages being received by our Azure Bus subscription.
Upon investigation, we found that these messages are being triggered by Squidex CMS.
To identify the root cause, I performed several troubleshooting steps:
- Deleted all Rules – I suspected that failed events from Rules might be getting re-enqueued. However, even after deleting all Rules, messages continued to be added to the queue.
- Cleared all active messages in the queue – This did not resolve the issue, as new messages continue to be added.
Additional observations:
- Logs indicate that messages are being generated repeatedly for the same document that previously had processing failures in our code (this issue has now been fixed and is working correctly).
- Messages are being successfully processed and marked as completed.
I also observed that when we have renamed RuleEvents collection in MongoDB as RuleEvents_old and created new one, the issue for repeated message is resolved.
I want to know is it safe to clear out RuleEvents and it will not impact any other functionality in Squidex CMS?
We would greatly appreciate your assistance in identifying the root cause of this behaviour.