Hey! Nothing is broken here, let me break down what you're seeing:

• "Current Usage" is your total raw resource consumption for this billing cycle. "Estimated Bill" is what you'll actually be charged after your plan's included usage is applied, so the bill is the number that matters.
• Your services are paused because your Compute usage crossed the Compute hard cap you set ($35). That's the hard cap doing exactly what it's meant to. To bring services back online, raise the Compute limit (or wait for the next cycle to reset it) under Usage → Update limits.
• On the agent usage ($1.93): the build/deploy agent can run automatically in some flows (e.g. when a build fails), which is most likely where that came from. The reason setting the agent cap to $0 is rejected is that a hard cap can't be set below usage you've already incurred this cycle; you can set it to $2 now and lower it next cycle.

Want me to apply a one-time credit for the $1.93 of agent usage since it wasn't intentional? Happy to. Let me know if the breakdown clears things up.