SF Case not created, strange error in CloudWatch

[chrisansotti]

Just completed configuring VMX2 in a production instance but no cases are getting created and I'm seeing a weird error in CloudWatch (below). The recordings and transcriptions are making it into the S3 bucket in AWS, but no Case in SF. I've triple checked the settings and compared them to the sandbox where everything is working perfectly, can't see any config issues.

Field Value @ingestionTime 1664511723046 @log 246162452998:/aws/lambda/VMXPackager-goloprod00d6g000000ttsy @logStream 2022/09/30/[$LATEST]b51ec9c54c4c40d9aeca6993fcb74f4f @message [ERROR] 2022-09-30T04:21:59.975Z 1bb14ec3-84c3-42fe-b531-0e4dfb289be1 list indices must be integers or slices, not str @requestId 1bb14ec3-84c3-42fe-b531-0e4dfb289be1 @timestamp 1664511719975

[dougjaso]

Is this voicemail going to a queue or to an agent?

Sent from my iPhone

On Sep 29, 2022, at 9:37 PM, chrisansotti @.***> wrote:



Just completed configuring VMX2 in a production instance but no cases are getting created and I'm seeing a weird error in CloudWatch (below). The recordings and transcriptions are making it into the S3 bucket in AWS, but no Case in SF. I've triple checked the settings and compared them to the sandbox where everything is working perfectly, can't see any config issues.

Field Value @ingestionTime 1664511723046 @loghttps://github.com/log 246162452998:/aws/lambda/VMXPackager-goloprod00d6g000000ttsy @logstreamhttps://github.com/logstream 2022/09/30/[$LATEST]b51ec9c54c4c40d9aeca6993fcb74f4f @messagehttps://github.com/message [ERROR] 2022-09-30T04:21:59.975Z 1bb14ec3-84c3-42fe-b531-0e4dfb289be1 list indices must be integers or slices, not str @requestidhttps://github.com/requestid 1bb14ec3-84c3-42fe-b531-0e4dfb289be1 @timestamphttps://github.com/timestamp 1664511719975

— Reply to this email directly, view it on GitHubhttps://github.com/amazon-connect/amazon-connect-salesforce-scv/issues/141, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJRHYXTRD422MZHEPHRVI73WAZVAZANCNFSM6AAAAAAQZL5KTY. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[chrisansotti]

Going to a queue. I made sure they all have descriptions, too.

[dougjaso]

Did you deploy the solution as a Production (not Sandbox)?

Also, if this is a new Implementation, you should really consider using the included voicemail option that comes with the winter release, which is scheduled to be in all pods mid-october.

[chrisansotti]

Yes, assuming you mean the parameter setting in this screenshot:

[dougjaso]

Send me an email with availability for today. We can hop on and troubleshoot

[dougjaso]

In this case, we had to set the visibility for the custom fields. Interesting to see if others experience this. Perhaps something new with Winter.