Hard-coded Recipe ID ("flow_id") in Call recipe (asynchronous) action

The "Call recipe (asynchronous)" action in the Callable recipes by Workato app appears to hold a hard-coded recipe ID for the called recipe, which makes the exported metadata impossible to import into a new Workato team.

For organizations like ours where we have several environments set up for development, QA, UAT and Production, the ability to export and import recipes is critically important.

Analysis

What's strange is that the "Call recipe (synchronous)" action does not hard-code the Recipe ID ("flow_id"). Below is the relevant "flow_id" metadata from the synchronous action.

          "flow_id": {
            "zip_name": "src/util/convert_netsuite_categories_purchased_to_salesforce_products.recipe.json",
            "name": "Convert NetSuite Categories Purchased to Salesforce Products",
            "folder": "src/util"
          },

And in contrast, see the simple, hard-coded metadata from the asynchronous action.

              "flow_id": "642497",

Steps to reproduce

1. Create a callable recipe. What the recipe does is irrelevant.
2. Create a normal recipe using the Scheduler app for the trigger.
3. Add a "Call recipe (synchronous)" action that calls the callable recipe
4. Add a "Call recipe (asynchronous)" action that calls the callable recipe
   
5. Export the recipes just created. The metadata will show that "flow_id" is hard-coded in the asynchronous action but not in the synchronous action.