Currently, all runs are fetched in a single API call that includes serializableOutput and binaryOutput fields, which can be very bulky and slow down the initial load. Instead, these fields should be excluded when fetching all runs, and only fetched on demand when the user expands a specific run to view its captured data, storing the result in state. For example, expanding the below shown robot's run should fetch the data on demand.
Currently, all runs are fetched in a single API call that includes
serializableOutputandbinaryOutputfields, which can be very bulky and slow down the initial load. Instead, these fields should be excluded when fetching all runs, and only fetched on demand when the user expands a specific run to view its captured data, storing the result in state. For example, expanding the below shown robot's run should fetch the data on demand.