sfcc-platform-limits

Identify and mitigate SFCC quotas and limits across storefront controllers, OCAPI hooks, and jobs.

27|9|Updated Aug 8, 2025
One-click install
npx skills add https://github.com/taurgis/sfcc-dev-mcp --skill sfcc-platform-limits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sfcc-platform-limits
Source: https://github.com/taurgis/sfcc-dev-mcp/tree/main/ai-instructions/skills/sfcc-platform-limits
Command: npx skills add https://github.com/taurgis/sfcc-dev-mcp --skill sfcc-platform-limits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SFCC limits are not "edge cases"; they shape correct architecture. This guide helps teams recognize limit symptoms and apply reliable patterns to keep systems responsive and scalable.

Core Features & Use Cases

  • Identify execution context distinctions (storefront controller vs hook vs job) to ensure safe boundaries.
  • Recommend design patterns: move heavy work to asynchronous jobs, cache aggressively, and keep external calls bounded.
  • Provide concrete guidelines for common pain points like timeouts, CO quotas, and HTTPClient call caps with practical remediation examples.

Quick Start

Apply quota-aware design practices to your SFCC projects by prioritizing async processing, caching, and workload offloading.

Frequently Asked Questions about sfcc-platform-limits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid SFCC OCAPI hook timeouts and quota exceeded errors?

To avoid SFCC OCAPI hook timeouts, identify the execution context and move heavy logic to asynchronous jobs. Bounding external HTTPClient calls and caching aggressively ensures operations stay within platform limits.

What are the common SFCC platform limits that cause storefront controller failures?

Common SFCC storefront controller failures stem from CO quota exhaustion, outbound HTTPClient call caps, and script execution timeouts. Recognizing these limit symptoms early allows teams to apply caching and async workload offloading.

How do I design SFCC jobs to respect custom object quotas and prevent timeouts?

Design SFCC jobs to respect custom object quotas by enforcing bounded external calls and processing data asynchronously. Aggressive caching and workload offloading prevent timeout threats and maintain system stability during execution.

Does SFCC WebDAV usage have specific quotas or limits I need to monitor?

SFCC WebDAV interactions are subject to overarching platform quotas and timeout constraints. Applying bounded external call patterns and caching strategies helps manage these limits and ensures stable file operations.

What is the best way to handle SFCC HTTPClient outbound call caps in custom code?

Handle SFCC HTTPClient outbound call caps by enforcing bounded external calls and caching responses. Moving network-intensive operations to asynchronous jobs prevents synchronous storefront or hook blocking.

Can I use synchronous processing for OCAPI hooks without hitting SFCC execution limits?

Synchronous processing in OCAPI hooks risks hitting SFCC execution limits and timeouts. Moving heavy work to asynchronous jobs and caching data ensures hooks remain responsive and within platform boundaries.