2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Is your computer's time correct? If it is, please open a support case.
0
I figured out why this is happening -- the redirect URL after starting another execution has an invalid date format. The end of the URL says startDate=<date> but <date> is in a URL encoded string format when it should be a long integer.
I wrote a Chrome Extension to fix it as a workaround until AWS fixes it. See https://github.com/rogerjaffe/aws-step-function-fix. The details are in the Readme file
répondu il y a 4 mois
Contenus pertinents
- demandé il y a 2 mois
- demandé il y a 7 mois
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
Yes, the time is correct -- thank you for the answer. And unfortunately I only have basic support so I'm unable to open a support case. So I either live with it or spend $29 to upgrade my support plan. Unless you know of a different way.
And I've disabled all Chrome extensions on a hunch with no effect. But the problem happens on Firefox and Opera where I have no browser extensions enabled.