2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
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
답변함 4달 전
관련 콘텐츠
- AWS 공식업데이트됨 일 년 전
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.