Karolis Pocius

Looks like the issue got fixed via https://github.com/opsgenie/terraform-provider-opsgenie/pull/413

Same here. We have a mix of archived and non-archived groups, so it gets super confusing and we need to double-check each time that we don't accidentally turn off the...

This is curious. API does indeed return `"isArchived": "true",` for the affected groups, but it's definitely off in the UI 

It does indeed sound like an API issue. Especially since it's rather inconsistent. I'll reach out to Google, cheers.

Google Workspace support told me to contact GCP support because we use SA to authenticate the provider (weird, but OK). Still haven't heard back from GCP support though.

The issue has been resolved by Google. Provider is now working as expected again.

~When you get the error, applying again helps, but as soon as you make any other changes to the repo, you get the error again and have to apply a...

As explained on #63: > It evenly balances the partitions across the brokers, and any "extra partitions" are evenly distributed within the cluster. I believe that's what SSH'ing is for...