Sometimes limits prevent changes, sometimes they prevent saving

This requires more investigation:

• Sometimes, we disable buttons with messages that say stuff like: "you can't perform this action because you don't have credits/permissions/etc."
• Sometimes, we throw validation errors on save with messages that say stuff like: "you can't save this workflow because it's not in a valid state"

The second thing happens, notably, when you attempt to enable a workflow and later press save — if you're past your limit when you click save you get an error. We could disable the enabled switch instead.

The issue names no files, tests, or entry points. Start by tracing the workflow enable action and the later save validation, then compare how credit or permission limits are handled in each path. Done means the project has an agreed, consistent behavior for preventing the change or rejecting the save.