rhythmic-beach-70913
03/26/2024, 4:25 PMFlow.runs() doesn't seem to help because it doesn't return that many runs and we have thousands of runs of the same flow over time - filtering by tag doesn't help (and is a bit tricky because it's step functions anyway)
Tangentially related I'm also finding it hard to tell if a flow has failed - .finished isn't being set to true when it fails
The UI seems to be able to cope so any ideas how to do this in python?
The names of the step functions are quite long so usually get truncated as well so that's another complication which makes it tricky to query the step function instead - I will be able to do that but hoping there's a easier way than parsing the output when it's deployed
Thanks!dry-beach-38304
03/26/2024, 4:44 PMnamespace(None) to get all runs.dry-beach-38304
03/26/2024, 4:44 PMfinished, we have had a lot of internal debates about this.dry-beach-38304
03/26/2024, 4:45 PMdry-beach-38304
03/26/2024, 4:45 PMdry-beach-38304
03/26/2024, 4:46 PM.exception that you can check too.dry-beach-38304
03/26/2024, 4:46 PM.finished will return true if the task finished without uncaught exception.rhythmic-beach-70913
03/26/2024, 4:47 PMdry-beach-38304
03/26/2024, 4:48 PM.exception (and yes, the doc string for that is also highly confusing)rhythmic-beach-70913
03/26/2024, 4:50 PMrhythmic-beach-70913
03/26/2024, 5:03 PMnamespace(None) has probably done the trick - thanks