temporal-rules

Temporal Workflow Rules

Project Context

• This project uses Temporal.io for workflow orchestration
• Temporal Server version: 1.29.2
• Temporal Admin Tools: 1.29.1-tctl-1.18.4-cli-1.5.0
• Temporal UI: 2.44.1
• All services connect to Temporal for long-running business processes

Workflow Architecture

Workflow Locations

• Workflow definitions: apps/*/src/workflows/
• Activity implementations: apps/*/src/activities/
• Shared workflow utilities: packages/workflows/src/lib/
• Temporal configuration: apps/*/src/config/temporal.config.ts

Worker Configuration

• Each NestJS app runs its own Temporal worker
• Workers are initialized in the main application bootstrap
• Task queue is configured per service via environment variables
• Workers bundle workflows using Webpack

Workflow Patterns

Workflow Definition

import { proxyActivities } from '@temporalio/workflow';
import type { ActivitiesService } from '../main';
const activities = proxyActivities<ActivitiesService>({
  startToCloseTimeout: '1 minute',
});
export async function myWorkflow(input: WorkflowInput): Promise<WorkflowOutput> {
  // Workflow logic here
  const result = await activities.myActivity(input);
  return result;
}

Activity Definition

@Injectable()
export class ActivitiesService {
  constructor(
    private readonly prisma: PrismaService,
    private readonly emailService: EmailService,
  ) {}
  async myActivity(input: ActivityInput): Promise<ActivityOutput> {
    // Activity logic with side effects
    return result;
  }
}

Critical Rules

Workflow Code Constraints

• ❌ NO direct database calls in workflows
• ❌ NO HTTP requests in workflows
• ❌ NO file I/O in workflows
• ❌ NO random number generation in workflows
• ❌ NO Date.now() or new Date() in workflows
• ✅ YES to deterministic logic only
• ✅ YES to calling activities for side effects

Use Activities For

• Database operations (Prisma queries)
• HTTP/API calls
• Email sending
• File operations
• Any non-deterministic operations
• External service integrations