O governance.py usa a tabela action_log para contar ações dentro da janela: 80%: Info log — \"Approaching rate limit\" 90%: Warning — \"Near rate limit, consider s
The Rate_Limits skill monitors and enforces Instagram Graph API usage limits to prevent exceeding thresholds that result in errors or blocked requests. It tracks API calls, content publishing, hashtag searches, DMs, and stories within defined sliding time windows, logging warnings as usage approaches limits. When limits are reached, it triggers backoff strategies including automatic retries with exponential delays or longer waits depending on error codes.
This skill integrates detailed rate limit rules from Instagram’s API, including hourly and daily caps per user or account, and implements intelligent batching and local caching to optimize request efficiency. It ensures that API interactions remain within allowed quotas, reducing downtime and improving the reliability of social media automation workflows.
This skill is designed for social media performance marketers managing Instagram at scale, growth leads coordinating multi-account publishing, and agency strategists responsible for client campaigns that rely heavily on API-driven content and data syncs. It suits teams that automate posting, hashtag research, and messaging workflows, where hitting Instagram’s rate limits could disrupt campaign timing or data freshness.
It is also valuable for SEO/PPC operators integrating Instagram insights into broader reporting dashboards, needing consistent data without being throttled by API restrictions. Anyone orchestrating batch data pulls or large-scale content management on Instagram will find this skill essential to maintain smooth operations.
Practitioners start by tracking API usage metrics in real time through the action logs, querying counts of requests, posts, hashtag searches, and messages within defined windows. As usage approaches 80% and 90% of limits, they review info and warning logs to decide whether to throttle activity.
Next, they implement backoff procedures triggered by different error codes, such as a 1-hour wait on application-level or user-level rate limit hits, with exponential retry delays for transient failures. They optimize calls by batching field requests and caching recent data locally to reduce redundant queries.
Finally, they prioritize sync order—first profiles, then media, insights, and comments—using limits to control how many posts are processed per run, balancing data freshness against staying within quota. This sequence minimizes risk of hitting hard rate limits while maintaining comprehensive data coverage.
How do I know when I’m close to hitting a rate limit? The skill logs info at 80% and warnings at 90% of your quota, giving time to adjust activity. What happens if I hit an error code 4 or 17? The skill automatically backs off for one hour before retrying to avoid further failures. Can I reduce the number of API calls made? Yes, batching requests with multiple fields and caching recent data locally both help minimize total requests.
Attach the Rate_Limits skill to your Metaflow agent task to automatically monitor Instagram API usage based on your action logs and enforce backoff policies when thresholds are exceeded. Expect detailed logging of usage percentages and automatic retry handling for common rate limit error codes. This skill works seamlessly with your existing Instagram workflows to ensure stable API interactions while maintaining efficient data syncs and content publishing. You can get started by...
For broader context, see our roundup of claude skills marketing, and read best Claude Code setup for marketing teams for related setup guidance.