Issue Summary

When importing an automation rule that has invalid Okta connectors, it shows as "successful," even though there are errors in the network tab and the rule isn't imported at all. This message is misleading.

Steps to Reproduce

1. Export an automation rule that has any Okta connector component.
2. The exported JSON must be invalid, either by manually changing it or disabling the connection.
3. Import the rule. 

Expected Results

If there's a problem with the JSON, an error message must be returned. 

Actual Results

The rule shows as "imported", even though it wasn't, and there's an error in the network tab: 

Workaround

Create the automation rule from scratch, or ensure the Okta connector component is valid.