oponomarov-tu

Any update on this? 🙏

Should stay open.

I did some more digging and reverting PagerDuty provider to version `~> 2.16.0` (2.16.2) did the trick, it all works again. Apparently, version 3.7.1 could create a brand new escalation...

~~I can confirm v3.11.2 resolved the issue. Thanks! ❤️~~ @imjaroiswebdev, actually, looks like it is not resolved. Still failing to modify the resource in-place: ```hcl module.pagerduty.pagerduty_escalation_policy.team_oncall_escalation_policy: Still modifying... [id=, 20s...