Backups not working

[mick-shaw]

I've deployed this example but the backup flows button doesn't seem to work. I see no DDB entries in either the ARN mapping table or the Contact Flow table. The UI grabs the flows from both instances just fine. Can someone point me in a direction? It looks as if there's a single lambda that performs all the work but see no logs in cloudwatch other than when it was deployed. The only deviation from the documented example is that I'm using two connect instances in the same AWS account versus two instances in separate accounts.

[ramprasadsv]

Hello Mick,
There is no lambda function involved in the solution, everything happens thru the UI that you are using to execute the API's leveraging AWS SDK for JavaScript.

1. You have to configure the ARN's in the ARN mapping table, for ex. Queue/Prompt/Lambda/Contact Flows. Basically, on the left panel is your source instance, you need to configure target instance resource ARN's.

2. Can you please check on the DDB(for the backup, default name is "contactflow") to ensure it has "Primary partition key" as "flowId" and "Primary sort key " is not configured in the overview tab. If it has the "Primary sort key" please drop the table and recreate table ONLY with "Primary partition key" as flowId.

[mick-shaw]

The contactlow table was created with a sort key. I recreated the table with just a primary key of flowId, as suggested. However, I'm still not able to back-up flows and nothing is writing to contactflow table. Any additional recommendations would be appreciated. This is a tool I've wanted/needed for some time.

[sajan11]

Hi, Just to let you know, I've recreated another DynamoDB table without the "Primary Sort Key" and this works. I was able to backup the contact flow to the DynamoDB. Make sure to update the DynamoDB name on AWS configurations.