Closed gordonwatts closed 3 weeks ago
This worked in the 2.0 client, but perhaps this is a non-goal now, @ponyisi ?
The reason it comes up is that sometimes running these really big datasets you can have an hour or more in time, and it is very easy to get a disconnect when that happens.
It's a goal but I think we should make it a 3.0.1 or 3.0.2 feature? Basically, look in the local cache for a submitted but not completed transform and recover state from that.
I've updated the list for client caching - https://github.com/ssl-hep/ServiceX_frontend/issues/280#issuecomment-2327264275
Feel free to move this to another milestone!
The following sequence:
Expected behavior: