Yes, I did find the google-able documentation, but I wasn't sure if the API worked or not, or it was just a temporary vision of the future, etc -- I guess I sim

Yes, I did find the google-able documentation, but I wasn't sure if the API worked or not, or it was just a temporary vision of the future, etc -- I guess I simply didn't try. :) Perhaps once my GH Actions Workflow is figured out I can migrate to this, and open source it (though it's tied up with my OCaml code at the moment...) > Are you actually observing non-negligible cold start times, though? Usually the cold start time is so low that you can't really tell when it happens. Honestly, no, it was just something I realized when writing my workflows -- that I don't know from the API how to tell if a worker is "up to date or not" other than downloading and comparing. All of my tests have been exceedingly simple (for now) so it was more just a cautious pre-optimization to make sure I didn't tank something later on a script unrelated to the one I was working on (my workflows upload all scripts across domains during CI, iff they changed). Oh! Here's one more feature request, though: atomic route/filter updates for scripts would be really nice. Right now I kind of iterate through them and match/delete/update them one by one, because overlapping routes cause errors. This means actually doing an insert or update or create is a bit complicated -- you need to actually grab the list of existing routes up front and match IDs with the corresponding route paths, before you can determine what to do (if it already exists, update, if it no longer exists, delete, otherwise, insert, etc) But it would be a huge simplification if I could say "Atomically replace the current routes with this set of routes all at once". I'm not sure how easy this is on your end, though. Now that I think of it, I guess I can just immediately wipe and insert a whole new set, though, since it's not like the current solution is atomic anyway!