Can I capture Execution context from an actionable interceptor?

[Overdash]

I want to report errors to a upstream Error Monitoring service (i.e. posthog) whenever a route or Server Action fails.
I'm using nextjs and currently have an instrumentation.ts and error.tsx setup to catch global errors, but oRPC errors don't seem to propagate to them, i.e. take this handler:

export const errorCheck = publicProcedure
  .input(z.object({ trigger: z.boolean() }))
  .handler(async ({ context, input, errors }) => {
    const { logger } = context
    const { trigger } = input
    logger.warn(`Incoming error check...? ${trigger}`)

    if (trigger)
      throw errors.PANIC({
        message: "Error Check",
      })

    return trigger
  })
.actionable({ context: { source: "server_action" } })

The panic error is never reported to my aforementioned ErrorBoundaries when ran as a server action.

  const { execute } = useServerAction(errorCheck)
// ...
  await execute({ trigger })

I tried slapping on an onError interceptor to the actionable, but then I'm unable to access the execution context, so I can't track who made the request.

So I have 2 Questions:

1. What is the best way to handle global errors from actionables?
2. How do I access the execution context from the actionable interceptor?

(Read this discussion for the client side: #240)

[unnoq]

You can do it with middleware or interceptors (with onError that placed in second arg)

[Overdash]

Right, but that only picks up the Initial Context doesn't it?
I can't grab the Execution/Runtime Context from that arg (despite the docs recommending to use Runtime ctx with Server Actions)

[unnoq]

So I think middleware will match your use case, If you don't know you can use Middleware Dependent context for require .use after an auth middleware for example.

[Overdash]

Ahh!! That's brilliant, thank you - sorry for the silly question! :)

P.S. great library, loving the flexibility - switched over from tRPC so trying to get everything in parity :D