Bug: IdempotencyPersistenceLayerError cause undefined

[jorgecamilowu]

Expected Behavior

When looking at the logs, the cause attribute of IdempotencyPersistenceLayerError should include what actually went wrong.

Discord discussion link

Current Behavior

The cause attribute of IdempotencyPersistenceLayerError is undefined

Code snippet

const persistenceStore = new DynamoDBPersistenceLayer({
  tableName: "Token.1234",
});

export const handler = makeIdempotent(handlerFunction, {
  persistenceStore,
});

Steps to Reproduce

1. Pass an invalid table name to DynamoDBPersistenceLayer such as "Token.1234"
2. Trigger the lambda
3. See IdempotencyPersistenceLayerError error in Cloudwatch logs missing the cause attribute
   

Possible Solution

No response

Powertools for AWS Lambda (TypeScript) version

2.7.0

AWS Lambda function runtime

20.x

Packaging format used

npm

Execution logs

2024-08-12T06:04:28.165Z	1ecc73f4-1b73-4bf0-bf92-d8fd26a123d6	ERROR	Invoke Error 	{
    "errorType": "IdempotencyPersistenceLayerError",
    "errorMessage": "Failed to save in progress record to idempotency store",
    "name": "IdempotencyPersistenceLayerError",
    "stack": [
        "IdempotencyPersistenceLayerError: Failed to save in progress record to idempotency store",
        "    at #saveInProgressOrReturnExistingResult (/var/task/index.js:1459894:13)",
        "    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)",
        "    at async IdempotencyHandler.handle (/var/task/index.js:1459814:42)"
    ]
}

[boring-cyborg]

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #typescript channel on our Powertools for AWS Lambda Discord: Invite link

[dreamorosi]

Hi @jorgecamilowu, thank you for taking the time to open this issue, and for finding the bug in the first place.

I have started working on a PR that should address the issue.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.