Long running test plans can easily exceed max execution history size

[pjenvey]

Long running test plans (say =~ 11 hours) can trigger so many check_for_cluster_done checks that they can exceed the Step Function maximum execution history size (currently 25,000).

This will cause the test plan to stop with an output JSON (seen in the UI's Execution Details Output tab) of:

{
  "error": "States.Runtime",
  "cause": "The execution reached the maximum number of history events (25000)."
}

Not to mention what's really a separate issue: the event history is largely impossible to scroll through for debugging purposes.

[veve90]

Totally agree on this point!!!