After taking a closer look on the log on our production environment convo-2021-01-05.log it seems that the problem occurs in mtg-database service.
Log snippet:
After observation of the workflow in 'mtg-database' service it seems that the following snippet triggered the media reqeust in AmazonCommandRequest which is wrong:
After taking a closer look on the log on our production environment convo-2021-01-05.log it seems that the problem occurs in mtg-database service. Log snippet:
After observation of the workflow in 'mtg-database' service it seems that the following snippet triggered the media reqeust in AmazonCommandRequest which is wrong:
Final conclusion is that the method isMediaRequest in AmazonCommandRequest delivers wrong result when some of the following intents occur:
For this particular case it was AMAZON.PreviousIntent in 'mtg-database' service.