Cursor rule

1---
2description: Rules for working in the Worker service (background job processing)
3globs: apps/worker/**/*
4alwaysApply: false
5---
6 
7## Worker Service
8 
9**Stack:** NestJS · Bull + Redis · ClickHouse (execution traces) · cron-parser
10 
11**Run:** `pnpm start:worker` — only needed when testing notification triggering; skip for dashboard/API-only tasks.
12 
13**Tests/lint:** see testing.mdc
14 
15**Key directories:**
16```
17apps/worker/src/app/workflow/usecases/   # Workflow step execution usecases
18apps/worker/src/app/workflow/services/   # Queue consumers and job handlers
19```
20 
21---
22 
23### Worker Service Conventions
24 
25**Use-case structure**
26- Each notification channel has a dedicated `send-message` use-case under `apps/worker/src/app/workflow/usecases/`.
27- Follow the CQRS pattern: `execute(command: CommandClass)` returning a typed result.
28- Keep channel-specific logic isolated — do not share send-message logic across channels.
29 
30**Queue / Bull**
31- Job consumers are registered in NestJS modules using Bull's `@Process` decorator.
32- Retry logic and failure handling are configured at the queue level in `libs/application-generic` — do not duplicate this in worker use-cases.
33- Always handle job failures gracefully and log execution details via `CreateExecutionDetails`.
34