2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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
répondu il y a un an
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
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?