Skip to main content

In our DEV environment, we are generating the export of selected items, either via Control Room or API, always selecting the "Production label."

However, when we import this into our homologation environment, we encounter dependency breaks.

 

For example:

 

• We have a parent task with 10 versions, and version 8 is set as Production

• We generate the export using the Production Label • When importing into the homologation environment, we receive a dependency break error, referencing child tasks that are on version 10

• Because of this, we understand that the Production label selection is not being respected, as it always carries forward the latest available version

 

Is this the expected behavior, or are we doing something wrong in our procedure?

double check. Make sure you have new package versions imported too.

That’s an interesting question, Vinicius Amorim !

I think the following community members may be able to help 

@Vatsy 

@Tamil Arasu10 

Hi ​@Vinicius Amorim,

✅ Workarounds

Here are a few approaches to mitigate this:

1. Manually Align Versions

Before exporting:

  • Ensure that all child tasks also have the correct version marked as Production.
  • Or, revert child tasks to the desired version before exporting.

2. Use Version Control Naming

Adopt a naming/versioning convention that helps you track which versions are safe to export.

3. Export Manually with Dependencies

Instead of relying on the label, manually select the correct versions of all dependencies during export.

4. Raise a Feature Request

If this behavior is problematic for your workflow, consider submitting a feature request to Automation Anywhere via their support or A-People portal

Reply


Terms & ConditionsCookie settings