Get Asset - CacheStrategy in Library

Help Orchestrator
, , , ,
1

Hi!

We’re currently designing several libraries and would like them to fetch their own assets instead of having the process fetch the assets and feed them into the library.

Will a Get Asset in a library (used by a process) with a CacheStrategy set to Execution guarantee that the asset is only fetched from the orchestrator once? I get that it will do that when the activity is directly in a process, but I was wondering if it is different when used in a library in the process.

2

@sven.wullum1

In library it would run always as whenever activity is called a new instance will be created

cheers

1 Like
3

Im pretty sure that since the library is initialized the moment the activity is run, the cache will always be a new one as well. But im not sure about it.

Either way, if you want to be sure, its better to get the asset from the process.

1 Like
4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.