Will Envio invalidate the TSV cache when the output is undefined?

[PaulRBerg]

Given an effect implementation like so:

export const fetchProxender = experimental_createEffect(
  {
    cache: true,
    input: S.tuple((t) => ({
      chainId: t.item(0, S.number),
      lockupAddress: t.item(1, S.string),
      streamSender: t.item(2, S.string),
    })),
    name: "proxender",
    output: S.union([S.shape(S.schema(0), (_) => NOT_AVAILABLE), S.string]),
  },

Full code here: https://github.com/sablier-labs/indexers/blob/4dc34c2fc7e013bcc6e9e7d9f5fc7ae6dc0782b0/envio/lockup/effects/proxender.ts

Will Envio attempt to refetch the data if the cache file references a NOT_AVAILABLE value?

If not, the data will forever be stuck as not available even if there might have been a temporary glitch in the API.

cc @DZakh

[DZakh]

Will Envio attempt to refetch the data if the cache file references a NOT_AVAILABLE value?

No. Cache is a key value storage, so unless input changes, it won't rerun the effect.

[PaulRBerg]

how to make it purposefully fail validation?

[DZakh]

You'll need to use S.transform for this. But in the current version, it'll simply crash instead of invalidating the data.

[PaulRBerg]

Thanks. Updating the docs once this is done will be helpful!

[DZakh]

Added output validation logic in the PR #789

[PaulRBerg]

TL;DR for how we will be able to use it in practice?