Request & System Flows
The exact data pathways for the platform's most critical operations.
Job-Easy relies on strict pipelines for core operations. These flow diagrams illustrate how data moves through the application, highlighting the specific fail-safes and architectural invariants at each step.
Authentication & Guard Chain
BrowserRequest arrives
Edge MiddlewareCookie presence check (fast fail without DB)
server/guards.tsDatabase session hash & expiry verification
The Gate ChainStatus → Maintenance → Subscription → Legal → Onboarding
ExecutionRoute handler or Server Component renders
User Outreach Sending
UserSelects company, template, and resume
MIME BuilderServer parses template and constructs RFC 2822 payload
Gmail APISends email natively via user's OAuth token
DatabaseWrites EmailLog hard snapshot (immune to cascade deletes)
PipelineCreates or links Application with Gmail threadId
Gmail Reply Synchronization
Pub/Sub WebhookGoogle pushes historyId delta notification
Gmail History APIFetches explicit message changes since last sync
Thread MatchingCorrelates new message threadIds to known Applications
State MachineUpdates Application status to 'Replied'
Decoupled Alertnotify() fires (failures here don't roll back the DB)
Account Deletion Pipeline
TriggerUser requests deletion OR Admin executes purge
Workflow LockStatus transitions to 'deleting' (irreversible)
OAuth RevokeGoogle access token actively revoked to prevent orphans
CDN PurgeCloudinary assets (resumes, avatars) permanently destroyed
Database CascadeTransactions delete User row and associated models