@jkabot interesting. I'll have to read up on that. Do you get control over cache expiration?

You can only specify the maximum life span (and netsuite might clear it before that). You have no guarantee over the minimum life span.

hmm, that may not be sufficient guarantee then for use in a script where one part is communicating data to another stage - and that other stage has no knowledge of how the cache data was set in the first place. Basically, using cache as a message passing construct doesn't sound reliable?

Doesn't sound like it. I currently use it for values that get calculated dynamically with searches but don't change very often in order to avoid running the search every time transaction gets loaded/saved