Catalyst Cache

How It Works

Before any MCP call, establish context once per session via the workspace readiness gate: ../catalyst-basics/references/preflight.md. It resolves and reconciles the org/project so CatalystbyZoho_List_All_Segments targets the right project.

1. Get Segment ID — Use MCP (CatalystbyZoho_List_All_Segments) if available; otherwise retrieve it from the console or .catalystrc.
2. Load references/cache-basics.md — for SDK operations, TTL limits (48 hr max), and the segment.delete() / segment.update() gotchas.
3. String values only — All cache values are strings. Always JSON.stringify before put and JSON.parse after get.
4. TTL behavior — segment.update(key, value) without an expiry argument resets the TTL to 48 hours (the max), not the key's original TTL. Always pass the TTL explicitly (in hours) to preserve it: segment.update(key, value, ttlHours). segment.delete() returns null (not an error) if the key is missing.

Triggers

Use this skill for: "Cache", "cache segment", "cache key", "cache value", "TTL", "in-memory store", segment.get, segment.put, segment.delete, "session data", "temporary data Catalyst", "cache vs Data Store", or "48-hour cache".

References