Environments Disabled after Upgrade

I upgraded my account from Team to Business and now my environments are disabled except production. How do I re-enable them?

Contact Retool support

Welcome to the community, @Bradley_Holbrook! I see that you already reached out to our Support team, but it's unclear whether they were able to help you out. Can you clarify what disabled means in this particular context? Are you unable to switch environments inside an app? What do you see on the /settings/environments page?

They didn't help no. I've had this account for years with applications running on it. We had the team account with 3 environments. At some point in the last 24 hours the environments disabled except for production (and all of our apps defaulted to production which caused some kaos today as a lot of our tools are built for resource management for QA testing teams who now where on production without knowing it)

I digress. Before I upgraded the account (which I saw as my only option to get my environments back) I saw production, testing / qa (disabled), and development (disabled).

In the app itself, both as an editor and viewer, those names persist as well.

After account upgrade to business, on the settings page they became enabled, but they still show disabled in the environment switcher in the bottom left. I cannot switch environments inside the app.

Thanks for the context. :thinking: I assume you haven't modified those apps recently, but can you double check that the contained resources all have a valid configuration for each environment? Looking at our internal database, it looks like there are a couple that only have a production configuration. It's certainly possible that there is some other underlying cause, but I'd rather eliminate the low hanging fruit first.

Well, yes you're right. We had 15 Prod, 9 testing and 10 development. But these were intentional. Some of our services only require a production copy because it's a wrapper application around an internal Google spreadsheet. There is no testing or development version of that document, or app for that matter. This is just an example. Prior to yesterday, this setup worked well. Do we now have to ensure that each data source has a configuration for each environment?

Only for resources that are being queried from your app. If you have an app with 10 resources but one of them only has a production configuration, you'll be prevented from switching environments in that app only.