Let us know how we can make Jedox even better!
Triggering a cube extract with a lot of rule-based values inside of it leads to a platform crash (in-memory DB exceedes max amount). A mechanism the stops the action instead of letting the action crash the system would be great. The platform should be more resistant to such events.
Thank you for your great idea. While we cannot commit to a specific target version, we will consider adding it to our future internal backlog.
My company had a similar experience in terms of outcome but with a different root cause, fixed by Jedox once identified but the underlying sentiment of this idea remains true, the solution just shouldn't ever be able to get to the point of completely crashing. There should be better safeguards in place to prevent this happening.