`Failed to import job script` error

[robcresswell]

Failed to import job script "../../src/job/job.ts": Cannot find module
'/app/node_modules/@sidequest/core/src/job/job.ts' imported from 
/app/node_modules/@sidequest/engine/dist/shared-runner/runner.js

Have you seen this before? The latest issue I've bumped into in trying to get sidequest set up. Seems to work locally, but something about my build process breaks it.

[GiovaniGuizzo]

You are trying to import a TS file. You must be able to run TS files with Node.js >= v23.6.0.

[robcresswell]

There's no src/job/job.ts in my codebase, and I'm reasonably confident the containers running node24+ (I'll check, so I dont waste your time)

[GiovaniGuizzo]

Then your machine is picking up jobs from other repositories

[robcresswell]

I think its the abstract job class requiring --experimental-transform-types to be set? Node doesn't natively transform that yet afaik

[GiovaniGuizzo]

It should use it by default in Node 24. The enum flag is optional, but Sidequest does not require it.

[GiovaniGuizzo]

Again, if you don't have a src/job/job.ts file in your repo, then your current Sidequest instance is picking up jobs from other applications. Maybe you are using a shared DB for many applications and they all use Sidequest?

[robcresswell]

strip-types and transform-types are not the same. The former is part of node 24, the latter is not, to my knowledge.

I don't think anything else is using sidequest; I added it to the system. It seems most likely that I'm registering something wrong, but I'm confused about how it could be working locally but not in prod. I assumed it was part of the build / runtime env.

[robcresswell]

Is there some mechanism in Sidequest that will remove that job entry after a while? I wonder if its stale data somehow.

[GiovaniGuizzo]

There is a mechanism that clears it every now and then, but it's a long time. It might be stale data indeed, but it should have failed and not retried after max attempts. If Sidequest is picking up those jobs again, then maybe they are new.

[robcresswell]

They are being added as new jobs, but I've still no idea where that src/job/job.ts path is coming from. The only mention of it is in the Sidequest codebase, but I don't understand how thats landing in the sidequest_job table. I don't have a src/job folder, or path, at all.

[GiovaniGuizzo]

Hummmm, something else is going on then. Now I get it. Sidequest is trying to automatically find your script path and is failing for some unknown reason, then it misinterpret it's own job script as the target.

I suggest you turn on Manual Job Resolution: https://docs.sidequestjs.com/jobs/manual-resolution

[robcresswell]

Managed to get the manual resolution working, things seem good now, thanks! Other than some issues about duplicate jobs. Unsure how to resolve scheduled jobs being duplicated. I thought that was handled by node-cron with noOverlap? Ive set .unique(true) as well.

[2025-12-11T23:13:30.020Z] [PID: 1] [NODE-CRON]
[ERROR] Job #undefined - RecurringJob is duplicated
DuplicatedJobError: Job #undefined - RecurringJob is duplicated

[robcresswell]

^^ I ended up ditching scheduled jobs entirely and just doing a setInterval for a common recurring task 😬 Couldn't figure out a nice way to handle scheduling jobs across multiple replicas without using manual db locks etc.