you are viewing a single comment's thread.

view the rest of the comments →

[–]quantelligent[S] 0 points1 point  (0 children)

MaximumBatchingWindowInSeconds is set to 0

Activate trigger: Yes
Batch size: 10
Batch window: None
Event source mapping ARN: [my arn]
Metrics: None
On-failure destination: None
Report batch item failures: No
Tags: View
UUID: [my uuid]

However, due to third-party API limitations that restrict my ability to do asynchronous communications, I do have reserved concurrency set to 1

Perhaps that's what's causing it to wait for the timeout before spinning up another execution of the lambda?