SQS Delete Message and Change Visibility fails with ReceiptHandleInvalid Randomly

[NalinKamboj]

Summary

My use case for SQS involves consumers taking a long time for completion, and the time range varies from 3-5 min to 15-20 min. I have set default visibility timeout to 2 minutes in AWS console, and here is my sqs-consumer config -

const sqsConsumerApp = Consumer.create({
  queueUrl:
    "<MY_URL>",
  handleMessage: async (message) => {
        // Process message work...
    }
  },
  sqs: new SQSClient({ region: REGION }),
  attributeNames: ["All"],
  messageAttributeNames: ["All"],
  visibilityTimeout: 120,
  heartbeatInterval: 110,
});

This works fine, but once in a while, I ran into an issue where the deleteMessage operation failed after the consumer finished. This led to the message being consumed again. This time, the changeVisibility operation failed. Surprisingly, the delete operation after consumer was done worked fine. I am not sure what's the issue here. Is my heartbeatInterval set too close to timeout?
Here are some logs for this case. You can see the error appear after cleanup function, then error handler is called with change visibility error. But after that, the cleanup function finishes and delete is successful (no error logs) -

{"level":30,"time":1682609106184,"msg":"Automation Cleanup Function - Cleanup complete! Status 2 applied to TaskID: 644933aafd98088ffbbb5abc"}
{"level":50,"time":1682609106736,"msg":"SQS Error handler called..."}
SQS delete message failed: Value <RECEIPT_HANDLE> for parameter ReceiptHandle is invalid. Reason: The receipt handle has expired.
Culprit -  {
  MessageId: '<MESSAGE_ID>',
  ReceiptHandle: '<RECEIPT_HANDLE>',
  MD5OfBody: '39db613b305601e25c09e28177e1b1e5',
  Body: '{"taskId":"644933aafd98088ffbbb5abc","newStatus":1}',
  Attributes: {
    ....<some attributes>
  },
  MD5OfMessageAttributes: 'e47abf401b87d3dbf4484f8ee3a2fa4c',
  MessageAttributes: { eventType: { StringValue: '0', DataType: 'Number' } }
}
// NEW MESSAGE appears with same message ID and RECEIPT Handle
{"level":30,"time":1682609106889,"msg":"New message received. MessageID: <SAME_MESSAGE_ID>"}
{"level":20,"time":1682609106889,"msg":"Message body parsed. MessageID: <SAME_MESSAGE_ID>"}
{"level":50,"time":1682609207944,"msg":"SQS Error handler called..."}
Error changing visibility timeout: Value <SAME_RECEIPT_HANDLE> for parameter ReceiptHandle is invalid. Reason: The receipt handle has expired.
Culprit -  {
  MessageId: '<SAME_MESSAGE_ID>',
  ReceiptHandle: '<SAME_RECEIPT_HANDLE>',
  MD5OfBody: '39db613b305601e25c09e28177e1b1e5',
  Body: '{"taskId":"644933aafd98088ffbbb5abc","newStatus":1}',
  Attributes: {
    ...<some attributes>
  },
  MD5OfMessageAttributes: 'e47abf401b87d3dbf4484f8ee3a2fa4c',
  MessageAttributes: { eventType: { StringValue: '0', DataType: 'Number' } }
}
{"level":30,"time":1682609407010,"msg":"Automation Cleanup Function - Cleanup complete! Status 2 applied to TaskID: 644933aafd98088ffbbb5abc"}
{"level":30,"time":1682609427774,"msg":"No messages to process at: 16:30:27"}
{"level":30,"time":1682609447984,"msg":"No messages to process at: 16:30:47"}

What seems to be the issue here? Can my heartbeatInterval and visibilityTimeout values be improved?
Thanks!

Example

No response

[nicholasgriffintn]

Not immediately sure what the issue is here but it's almost certainly something to do with timing.

On my list to think about.

[NalinKamboj]

What best practices would you suggest for setting the hearbeat and timeout values?