Assistance Needed with Amazon Echo Skill App Error

Hello Support Team, (@support_team)

I am encountering recurring errors in my logs related to the Amazon Echo Skill app. Could you please assist in diagnosing and resolving this issue?

Below are a few examples of the error messages:

app:282024-12-03 07:00:23.792 AMerrorError making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_96a1e795-47a9-4b56-add0-6b280f56f7e3_1733227223850.0..ASRLS_96a1e795-47a9-4b56-add0-6b280f56f7e3_1733227223850"},"payload":{"code":"INTERNAL_SERVICE_EXCEPTION","description":" AlexaDeviceStateStoreService returned an HTTP 503 error. Please engage AlexaDeviceStateStoreService owner to verify if their VIP is spilling over and/or there are no hosts behind the VIP."}}
app:282024-12-03 06:00:12.672 AMerrorError making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"ASRLS_cf1b42d7-f564-4752-8235-e72fd1bbc974_1733223612771.0..ASRLS_cf1b42d7-f564-4752-8235-e72fd1bbc974_1733223612771"},"payload":{"code":"INTERNAL_SERVICE_EXCEPTION","description":" AlexaDeviceStateStoreService returned an HTTP 503 error. Please engage AlexaDeviceStateStoreService owner to verify if their VIP is spilling over and/or there are no hosts behind the VIP."}}
app:282024-12-03 06:00:12.323 AMerrorError making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"48d1410e-b9e6-4eb8-9402-a085eeea1889"},"payload":{"code":"INTERNAL_SERVICE_EXCEPTION","description":"Internal service exception."}}

Relevant Details:

  • Hub Model: C7
  • Hub Version: 2.3.9.200
  • Connection: Wi-Fi with a static IP configured on the router

Thank you for your assistance. Please let me know if additional information is required.

Best regards,
David

503 is service unavailable - sounds like Amazon was/is having issues. Are you still seeing this?

3 Likes

I saw the same thing in my logs this morning, so I'm pretty sure it was an Amazon issue. No errors for the last couple of hours.

3 Likes

@thebearmay thanks for the reply. It looks like this just happened again about 15 mins ago.

app:282024-12-03 09:14:42.493 AMerrorError making Call to Alexa message gateway: {"header":{"namespace":"System","name":"Exception","messageId":"e70d6987-cbb5-4fba-8608-5d03029503c9"},"payload":{"code":"INVALID_REQUEST_EXCEPTION","description":"com.amazon.iota.container.exception.NoCorrelationSessionFound: No active session found for correlation token : SUdTVEs6AAE6AAg6eyJpZCI6Ijk0NWRjNTJjLTNhNDgtNGZlOC1hZDU0LTkyY2ViZjAzODVjZCIsInVyaSI6Imh0dHBzOi8vZC1hY3JzLW5hLXAtN2Q0LTU0ZmY2ZTQ4LnVzLWVhc3QtMS5hbWF6b24uY29tOjk0NDQiLCJzZXNzaW9uSWQiOiI2MmY4NzM5ZS1iYzJlLTQ1NzUtYTY4Ny05YzJiZGQ0OGM1NDcifQ=="}}

I see similar issues looking though the log on yesterday afternoon.

The Correlation Token error happens sporadically but doesn't seem to hurt anything - my guess is that a token refresh may not have gone through due to traffic or ??, but it always seems to recover.

2 Likes

Cool, thanks.