Skip to content
JamForce
Strategy & Guide ↓
FRIDAY · 4:55 PM

Org Meltdown

The architect has left for the weekend. Production hasn't. Route the chaos to the right tools and keep your org alive until 5 PM.

Jimmy CloudCo-Pilot

"It's 4:55. The architect's phone is ringing… at the beach. Ready to triage?"

⏱️
90s ShiftSurvive to 5 PM
⚡
3 BeltsInbox, Pipeline, Alerts
🛠️
8 ToolsAccess, Data, Deploy, Triage
📞
Lifeline3 Architect Calls
ARCADE SHIFT
90 seconds on the clock

Your shift starts here. Triage fast, build a streak, and call the architect when you need a lifeline.

123Switch Belts
QWER ASDFRoute Tools
SpaceCall Architect
Esc / PPause Game
🏆 High Scores
  1. No scores yet. Survive a shift!
Mission Debrief & Architectural Foundations

Why we built Org Meltdown

Org Meltdown puts you in front of the decisions Salesforce administrators and developers make when there's no time to look anything up. Each 90-second shift draws from 120 real-world production scenarios across three conveyor belts, and each belt represents a Salesforce design boundary.

Scenario ground rules
  • Answer the stated request using the eight tools. Automation cards ask what to build; Sandbox cards ask where to test. Access requests are approved, licences and prerequisites are available, and object or field access cards assume record sharing is already in place.
  • Data-quality requirements are the fictional org's business rules. For a simple formula-based save check, choose Validation Rule. Flow also supports before-save updates and can reject saves with Custom Error; choose Flow for the automation described.
  • Apex deployment cards use RunLocalTests unless stated otherwise: at least 75% overall coverage, some coverage for every trigger and all required tests passing. RunSpecifiedTests instead needs at least 75% on each deployed class and trigger from the selected tests.
  • A validated package has passed checks against the target, including dependencies, required tests and coverage, and has release approval. An eligible quick-deploy validation also has no intervening deployment and is within the 10-day window. Metadata-only changes do not inherit a blanket Apex coverage requirement.
  • Monday Pile is the game's prioritisation judgement for the stated deadline and impact. Salesforce does not enforce a Friday deployment ban.

The four reflex boundaries

Every ticket in the game reinforces one of these four foundational architectural choices:

Access Control

Permission Sets vs. Profiles

Q Perm SetW Profile
The Golden Rule: Additive permissions belong in Permission Sets. Restrictive baseline policies (login hours, IP ranges, session timeouts) stay on Profiles.
⚠️ The Friday Trap

Adding permissions to a shared custom profile for one executive grants those permissions to every user assigned that profile.

Read Users & Access Guide
Data Integrity

Validation Rules vs. Flows

E ValidationR Flow
The Golden Rule: Use Validation Rules for simple formula-based save checks. Flow supports before-save updates, after-save actions and Custom Error elements that can reject a save.
⚠️ The Friday Trap

Building automation for a simple field check adds unnecessary complexity. Use Flow Custom Error deliberately when validation needs branching or related data beyond a validation formula.

Read Declarative Business Rules
Deployment Safety

Sandbox vs. production gates

A SandboxS DeployD Reject
The Golden Rule: With RunLocalTests, an Apex deployment needs ≥75% overall coverage, some coverage for every trigger and all required tests passing. Test risky changes in a sandbox; use a preview sandbox for the next release.
⚠️ The Friday Trap

74% coverage is not 75%. Deploying untested packages straight to production because someone labelled it "urgent" is how weekend outages are born.

Read Testing & Deployment Guide
Triage Discipline

Immediate action vs. Monday Pile

F MondaySpace Lifeline
The Golden Rule: Vague requests, non-urgent schema changes, and ad-hoc ideas wait for regular business hours. Production emergency triage is only for live blockers.
⚠️ The Friday Trap

A late-Friday feature request still needs clear requirements and appropriate testing. Schedule non-urgent changes when people are available to validate and monitor them.

Read Change Management Guide

Keyboard controls & conveyors

Master hotkeys for split-second triage

Org Meltdown is designed for full keyboard control. Use number keys to switch incident belts and letter keys to stamp tools:

1 2 3
Switch Incident Belts[1] Inbox (Requests) · [2] Pipeline (Deploys) · [3] Monitoring (Data alerts)
Q W
Access ClusterQ Permission Set (Additive) · W Profile (Baseline/IP)
E R
Data ClusterE Validation Rule (Block at save) · R Flow (Automation)
A S D
Deploy ClusterA Sandbox · S Deploy (Approved & validated) · D Reject (Failed checks)
F
Triage ClusterF Monday Pile (Non-urgent / Unspecified requests)
Space
Emergency LifelineCall Senior Architect (3 charges max — 4th call hits beach voicemail!)

Jimmy Cloud's field guide

Production co-pilot tips for Grade S
TIP 1
Beware the 74% Coverage Trap!

"For a RunLocalTests Apex deployment, 74% overall fails the 75% minimum. Every trigger also needs coverage, and all required tests must pass. Stamp a failed package with D Reject."

TIP 2
Build Streak Multipliers for Huge Scores:

"Every 5 consecutive correct routings raises your multiplier by one step, up to ×5 at a streak of 20. Don't break the chain!"

TIP 3
Triage Early for Speed Bonuses:

"Cards resolved in the right half of the conveyor belt earn speed bonus points. Watch the tier: Tier 2 cards ride the belt 15% faster and Tier 3 urgent alerts 30% faster, so grab those first."

TIP 4
Practice Mode is Untimed:

"Want to study all 120 real-world cards without time pressure? Switch to Practice Mode from the title screen or debrief to drill your weaknesses."

Deepen your architectural knowledge

Each decision in Org Meltdown is taught in one of these guide sections:

Salesforce Fundamentals

Users, Profiles and Permission Sets, record access, and safe practice orgs.

Start this section →
Salesforce Admin Essentials

Solution design, org setup, declarative business rules, and data import and reconciliation.

Start this section →
Salesforce Administration

Org health monitoring, automation, testing configuration changes, and sandbox strategy and change management.

Start this section →
Salesforce Development Fundamentals

Apex, triggers and governor limits, bulk patterns, and testing and deployment.

Start this section →