2 Answers
- Newest
- Most votes
- Most comments
0
You indicate that you use timestampPath, which takes an absolute time stamp. Any chance that you give it the wrong time? I would recommend that you look at the execution log to see what is going on there.
0
Hello
it is the first thing I checked after I saw the thing. The timestampPath was good, and the function was suppose to wait only a few minutes
answered a year ago
Relevant content
- Accepted Answerasked 10 months ago
- asked 3 years ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 4 months ago
- What's the difference between Lambda function execution role permissions and invocation permissions?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Could it be a timezone issue? Does it start in the right minute, but the wrong hour? What does the logs show for this state?