Alexa Skills Spanish Variants Migration FAQ
To make your existing Spanish language skill available to Spanish-speaking customers in other countries, we are planning a language migration (copy over) of your existing live Spanish language skill to create an identical target Spanish language variant. See the following FAQs for information about the upcoming migration and please contact us if you have additional questions.
Frequently Asked Questions
1. What does migration mean?
To make your skill available to Spanish-speaking customers in other countries, we are planning a language migration (copy over) of your existing live Spanish skill to create an identical target Spanish language variant. Your skill will be available to ES and MX customers in the Spanish (ES) and Spanish (MX) languages subject to content policy guidelines.
2. What will happen to my skill as part of the migration?
We will create a target Spanish variant of your existing Spanish skill by copying all skill details, endpoint information, publishing information, and intent schema. We will then publish the multilingual skill to Spanish-speaking customers. You will not receive any certification feedback on your skill as part of the migration.
3. Is the migration going to create a new skill in the target Spanish language?
No, we will add a target Spanish language variant to your existing Spanish skill.
4. Are we planning to migrate and create non-Spanish variants of skills?
No. The migration plan is limited to copying Spanish skills to create the target Spanish variants.
5. Are all skills going to be migrated?
No, the migration will be applicable only to custom skills that a) do not use account linking, b) smart home skills c) do not use the Alexa Skills Kit built-in library in their intent schema, d) do not contain the target Spanish variant in development, certification, or live status, e) are eligible to be distributed to the target country, f) have skill endpoints that support the target Spanish locale, g) do not contain multiple APIs, h) are not built using the skill builder, and i) are not built using dialog management.
6. Why are we not migrating custom skills that use account linking?
We are not migrating custom skills that use account linking because we believe that developers of those skills would want to provide a more localized or custom experience for customers in the target Spanish language, and will manually migrate their skills as necessary.
7. Why are we not migrating smart home skills?
We are not migrating smart home skills because the skills implement account linking. We also believe that developers of smart home skills would want to provide a tailored skill experience in the target Spanish variant for their respective customers.
8. What if my skill went live post the migration cutoff date and therefore isn’t included in the migration?
If your skill is eligible, we will include it in the next round of migration. Future communications will include details about the skills to be migrated.
9. How can I opt out of this migration?
Provide your skill ID and skill name to help us identify the skills you would like to exclude from the migration. Opting out of the migration means that you will need to manually create a target Spanish variant and submit your skill for certification to make your skill available to the Spanish-speaking customers. Please contact us if you would like to opt out of this migration.
10. Are there any technical reasons/considerations to opt out of the migration?
One reason you may decide to opt out is if you will not be able to support increased traffic to your skill endpoint as customers interact with your skills in the target Spanish languages. Another consideration may be if your skill endpoint includes logic to check for existing live Spanish locale (language) attribute value at runtime before providing responses. In this case, your skill might not work as intended when the runtime locale (language) is set to target Spanish language. In this case, you can manually create the target Spanish variant of your skill and update your skill endpoint as needed.
11. Will the migration cause any adverse impact to the existing live Spanish skills?
No. The migration will not have any impact to the existing live Spanish version of your skill.
12. Do I have to do anything to my existing skill endpoint to support the migration?
No, we will use your existing endpoint when creating the target Spanish language variant of your skill. However, you should expect and plan to support increased traffic to your skill endpoint as customers interact with your skills in the multiple Spanish languages. If you believe your skill endpoint cannot support such increase in traffic, please contact us to opt out of this migration.
13. What if I manually create a target development Spanish variant of my skill prior to the migration?
If you manually add the target Spanish variant to your skill in the developer console and submit it for certification, your skill will be excluded from the migration. However, if you haven’t submitted your skill for certification with the newly added target Spanish variant, you can delete the Spanish variant from the development version of your skill and contact us prior to the communication cutoff date to be included in the migration.
14. Can I update the existing Spanish and/or target Spanish language variant of my skill after the migration?
Yes, once your skills have been successfully migrated, you can continue making updates to your Spanish variants of your skill and submit your multilingual skill for certification. We also recommend optimizing the sample utterances in the intent schema for your skill to enhance the experience for customers interacting with your skill in the target Spanish language.
15. Will the migration affect any changes that I have made to the development version of my existing Spanish skill?
No. We will not make any changes to the development or live versions of your Spanish skill.
16. What will be the state of my skill after migration has been completed?
Once we've migrated your skill, the live and development versions of your existing Spanish skill will continue to exist as-is. As part of the migration, we will create live and development versions of the target Spanish variant in your skill based on the information from the existing live Spanish version.
17. What happens if I use the ASK CLI or SMAPI to deploy updates to my skill?
The skill metadata and interaction models in the development console have been updated to support a new locale. Therefore if you try to use the
ask deploy command to deploy updates to the previous version of your skill you will get this error: "The local stored [skill] eTag does not match the one on the server side". If you try to use the
ask deploy --force command (ASK CLI v1) or the
ask deploy --ignore-hash command (ASK CLI v2), you will not have the migrated locale on your server side. You must first use the
ask clone -s SKILL_ID command to retrieve an updated version of the skill metadata and interaction models. You can then update your skill and use the
ask deploy command to deploy it to the development console.
For more about supporting multiple languages in a skill, see Developing Skills in Multiple Languages.