Returning scheduled function id

Am I trippin or losing my mind - is is not possible to schedule an action in a mutation and return the scheduled function id? As soon as I attempt to return

scheduledId

scheduledId

in the function below, both the function declaration

deleteUser

deleteUser

and the

scheduledId

scheduledId

variable incur the TS error

implicitly has type because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

implicitly has type because it does not have a type annotation and is referenced directly or indirectly in its own initializer.

export const deleteUser = authMutation({
  returns: v.id('_scheduled_functions'),
  handler: async (ctx) => {
    const scheduledId = await ctx.scheduler.runAfter(0, api.act.testAction)
    return scheduledId
  },
})

// act.ts
export const testAction = action({
  handler: async (ctx) => {
    console.log('hey')
  },
})

export const deleteUser = authMutation({
  returns: v.id('_scheduled_functions'),
  handler: async (ctx) => {
    const scheduledId = await ctx.scheduler.runAfter(0, api.act.testAction)
    return scheduledId
  },
})

// act.ts
export const testAction = action({
  handler: async (ctx) => {
    console.log('hey')
  },
})

djbalinOP•11/28/24, 12:30 PM

The logic works as intended if I just all the TS errors. What could cause this? I tried different permutations of file-function combinations, but didn't manage to find one that makes the error go away

This breaks types and intellisense though, so not really viable

RJ•11/28/24, 1:22 PM

See https://docs.convex.dev/functions/actions#dealing-with-circular-type-inference

RJ•11/28/24, 1:22 PM

This comes up sometimes, but it’s easy to fix

RJ•11/28/24, 1:24 PM

I believe you can also just annotate the return type of the action handler function

RJ•11/28/24, 1:25 PM

And that way avoid needing to annotate every usage of it

djbalinOP•11/28/24, 2:26 PM

Ahh thanks @RJ , it put me on the right path. My problem was different: the outer mutation (which schedules an action) could not have its type inferred correctly. What simply fixed it was this, i.e. explicitly adding this type to the variable . Maybe that's what you meant. Thanks man!

RJ•11/29/24, 5:17 PM

I meant this:

But glad you found a solution either way!