This happened to us at Hygraph when we released Components - a feature that lets you create reusable content templates. The feature is great, and users loved it, but, at times, a bit too much. The problem was that we've only noticed that the feature usage is kind of getting out of control, after our users started running into issues following this scenario:
One of the main and funniest issues is that we had almost no limits on the components usage because we've made a decision to cut them out of the initial scope to ship faster (or so we tell ourselves). Right now, of course, the effort to introduce the limits has tripled: not only do we need to put those limits in place, but we also need to
The thing that sucks the most is that you really cannot blame anyone but yourself. It is precisely my job to hunt for edge cases and guide users along the happy path of maximum value and zero bugs. Limits seem to be a great way to do that and, perhaps, to also encourage subscription plan upgrades. Is there a better way? I'll share my best guess here when we ship the next Components.