8 replies

Cache lookup function starts a new trace/span instead of inheriting caller context

When using

Cache

Cache

with a lookup function, it seems like the lookup function starts a new trace/isnt connected to the trace that triggered the lookup. Is that on purpose or a bug?

Communities Docs About Terms Privacy

Cache lookup function starts a new trace/span instead of inheriting caller context - Effect Community

Cache lookup function starts a new trace/span instead of inheriting caller context

Similar Threads

Cache lookup function starts a new trace/span instead of inheriting caller context

Similar Threads

Similar Threads

Similar Threads