Insights Automation: Imported automation configuration from production to sandbox/production , the lookupobject action still refering to the production schema

Issue Summary

When admin using the automation configuration that was imported from production to sandbox , the lookupobject action still referring to the production Insight schema. The same applies when admin copy the imported configuration. This is also applicable when an automation is exported and imported between 2 production instances.

Steps to Reproduce

1. In production, create a Insight schema called Schema A. ( If its a new instance , create a different object schema first , this is to assure the id will not match when we import it to Sandbox)
2. Then , create an object type and objects
3. Then, create automation and use lookupobject actions to search object in Schema A. Can us Name="xxx" iql. Add Log action to check the response value.
4. Now create sandbox instance.
5. Create Schema A in Insight and import the same data from production to Sandbox.
6. Now , export the automation from production and import it to Sandbox.
7. Execute the automation and monitor the log response.

Expected Results

It should return a different object key , based on Sandbox

Actual Results

Return the objectKey from Production insight.

Workaround

Open the imported automation configured , in the "Lookup Object" action , select a different schema and change it back to the original schema.