'Handle Apple Notes automation rate limits and iCloud sync throttling.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add jeremylongshore/tons-of-skills-marketplace --skill apple-notes-rate-limits --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Apple Notes Rate Limits?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeremylongshore-apple-notes-rate-limits-4a270983)More formats (shields.io, HTML) on the badges page.
---
name: apple-notes-rate-limits
description: 'Handle Apple Notes automation rate limits and iCloud sync throttling.
Trigger: "apple notes rate limit".
'
allowed-tools: Read, Write, Edit, Bash(osascript:*), Grep
version: 1.6.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- macos
- apple-notes
- automation
compatibility: Designed for Claude Code
---
# Apple Notes Rate Limits
## Overview
Apple Notes has no formal API rate limits like cloud services do. However, there are practical throughput limits imposed by three systems: the Apple Events IPC bridge (osascript to Notes.app), the iCloud sync daemon (`bird`/`cloudd`) that must process each write, and the Notes.app SQLite database that handles concurrent access. Exceeding these practical limits causes timeouts (-1712), sync lag, or data loss when writes outpace iCloud's upload buffer. This guide documents safe operation rates and provides throttling patterns.
## Prerequisites
- A tested Notes adapter that keeps note data out of command strings and logs.
- A bounded queue with an idempotency key or durable operation ledger for each write.
- An approved maintenance window and backup for bulk mutations; the rates below are conservative starting points, not a vendor guarantee.
## Instructions
1. Begin below the listed rates and increase only after observing successful sync on every required device.
2. Serialize writes and deletes; do not retry a timed-out mutation until a durable idempotency check determines whether it succeeded.
3. Pause the queue and escalate if timeout, sync lag, or duplicate detection crosses the service threshold.
4. Do not terminate iCloud processes to recover throughput; preserve evidence and use normal OS recovery procedures.
## Practical Rate Limits
| Operation | Safe Rate | Bottleneck | Exceeding Limit |
|-----------|----------|------------|-----------------|
| Create note | 1/second | iCloud sync buffer | Sync lag; notes missing on other devices |
| Read note (name/body) | 10/second | Apple Events IPC | -1712 timeout errors |
| Search (`.whose()`) | 2/second | Notes.app indexer | UI freeze; timeout |
| Move note between folders | 1/second | iCloud + local DB | Folder state inconsistency |
| Delete note | 1/second | iCloud delete propagation | Deleted notes reappear |
| Bulk list (all notes) | 1/10 seconds | Memory + IPC | Process killed by macOS |
| Attachment operations | 1/5 seconds | File I/O + sync | Corrupt or missing attachments |
## Throttled Operation Queue
```typescript
// src/rate-limit/throttle.ts
import { execSync } from "child_process";
interface ThrottleConfig {
minDelayMs: number;
maxRetries: number;
backoffMultiplier: number;
}
const THROTTLE_CONFIGS: Record<string, ThrottleConfig> = {
read: { minDelayMs: 100, maxRetries: 3, backoffMultiplier: 2 },
write: { minDelayMs: 1000, maxRetries: 5, backoffMultiplier: 2 },
delete: { minDelayMs: 1000, maxRetries: 3, backoffMultiplier: 3 },
search: { minDelayMs: 500, maxRetries: 2, backoffMultiplier: 2 },
};
async function throttledExec<T>(
operation: () => T,
type: keyof typeof THROTTLE_CONFIGS = "write"
): Promise<T> {
const config = THROTTLE_CONFIGS[type];
let delay = config.minDelayMs;
for (let attempt = 0; attempt <= config.maxRetries; attempt++) {
try {
const result = operation();
await new Promise(r => setTimeout(r, config.minDelayMs));
return result;
} catch (e: any) {
if (attempt === config.maxRetries) throw e;
console.warn(`Retry ${attempt + 1}/${config.maxRetries} after ${delay}ms: ${e.message}`);
await new Promise(r => setTimeout(r, delay));
delay *= config.backoffMultiplier;
}
}
throw new Error("Unreachable");
}
```
## Batch Operations with Rate Limiting
```bash
#!/bin/bash
# Batch create notes with throttling
INPUT_FILE="$1" # JSON array of {title, body} objects
DELAY=1 # seconds between creates
jq -c '.[]' "$INPUT_FILE" | while IFS= read -r note; do
title=$(echo "$note" | jq -r '.title')
body=$(echo "$note" | jq -r '.body')
osascript -l JavaScript -e "
const Notes = Application('Notes');
const n = Notes.Note({name: '$title', body: '$body'});
Notes.defaultAccount.folders[0].notes.push(n);
n.name();
" && echo "Created: $title" || echo "FAILED: $title"
sleep "$DELAY"
done
```
## iCloud Sync Monitoring During Bulk Operations
```bash
# Monitor iCloud sync backlog during batch operations
watch -n 5 'echo "=== Sync Status ===";
brctl status com.apple.Notes 2>/dev/null || echo "brctl unavailable";
echo ""; echo "=== Note Count ===";
osascript -l JavaScript -e "Application(\"Notes\").defaultAccount.notes.length" 2>/dev/null'
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| -1712 AppleEvent timeout | Operations sent faster than Notes can process | Increase delay between operations; use throttled queue |
| Notes reappear after deletion | iCloud sync restored note before delete propagated | Wait 5s after delete; verify deletion on another device |
| Duplicate notes created | Retry on timeout re-executed successful create | Track created note IDs; check before retry |
| iCloud sync stops during bulk ops | Sync daemon overwhelmed | Pause operations, preserve diagnostics, and use supported macOS recovery or Apple support guidance |
| UI becomes unresponsive | Too many Apple Events queued | Reduce concurrency; add `delay(2)` in JXA scripts |
## Output
The queue records operation type, opaque idempotency key, attempt count, latency, and outcome. It must not record note title, body, account identifiers, or raw Apple Event payloads. A bulk run ends with a reconciliation count and an explicit list of operations requiring review.
## Examples
For a planned import, enqueue one create at a time with a unique source-record key, wait for the configured delay, and reconcile the resulting note count before advancing. If a create times out, query the durable ledger and the scoped target folder before deciding whether to retry; never blindly submit the same create again.
## Resources
- [Mac Automation Scripting Guide](https://developer.apple.com/library/archive/documentation/LanguagesUtilities/Conceptual/MacAutomationScriptingGuide/)
- [Apple Events Programming Guide](https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/ScriptableCocoaApplications/)
- [iCloud Sync Architecture](https://support.apple.com/en-us/102651)
## Next Steps
For performance optimization beyond throttling, see `apple-notes-performance-tuning`. For monitoring sync health during operations, see `apple-notes-observability`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!