Is auth context passed to scheduled actions from server side queries/mutations?

I'm calling an action within a server side mutation using:

    await ctx.scheduler.runAfter(
      0,
      api.test.testFn,
      testData,
    );

    await ctx.scheduler.runAfter(
      0,
      api.test.testFn,
      testData,
    );

However when trying to retrieve the userIdentity within the action via:

    const identity = await ctx.auth.getUserIdentity();

    const identity = await ctx.auth.getUserIdentity();

It returns null.

Is the auth context only passed to the action when the action is called directly from the client? Or am I doing something wrong? I'm using Convex Auth btw.

Convex Community•2y ago•

8 replies

ninjz

Is auth context passed to scheduled actions from server side queries/mutations?

I'm calling an action within a server side mutation using:

    await ctx.scheduler.runAfter(
      0,
      api.test.testFn,
      testData,
    );

    await ctx.scheduler.runAfter(
      0,
      api.test.testFn,
      testData,
    );

However when trying to retrieve the userIdentity within the action via:

    const identity = await ctx.auth.getUserIdentity();

    const identity = await ctx.auth.getUserIdentity();

It returns null.

Is the auth context only passed to the action when the action is called directly from the client? Or am I doing something wrong? I'm using Convex Auth btw.

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Convex Community

Where Convex builders ask questions, share what they're building.

16,523 Members

Join

Is auth context passed to scheduled actions from server side queries/mutations?

Is auth context passed to scheduled actions from server side queries/mutations?

Continue the conversation

Convex Community

Continue the conversation

Convex Community

Similar Threads