DMSI Advanced API registers the following WP-Cron events on activation.
| Cron Hook | Schedule | Purpose |
|---|---|---|
dmsi_aapi_rate_limit_cleanup | Every 5 minutes (dmsi_aapi_five_minutes) | Deletes expired fixed-window counter rows from dmsi_aapi_rate_limit_counters |
dmsi_aapi_cleanup_jwt_blacklist | Daily | Deletes blacklist entries whose associated JWT has already expired |
dmsi_aapi_cleanup_oauth_tokens | Hourly | Deletes expired and revoked OAuth access and refresh tokens |
dmsi_aapi_key_expiry_check | Daily | Sends expiry warning emails for API keys expiring within the next 7 days |
dmsi_aapi_alert_evaluate | Every 5 minutes (dmsi_aapi_five_minutes) | Evaluates alert rules against recent API metrics and records triggered alerts |
dmsi_aapi_alert_cleanup | Daily | Purges alert history records older than 30 days |
dmsi_aapi_log_cleanup | Daily | Purges API request log records older than 30 days from dmsi_aapi_logs |
dmsi_aapi_daily_license_check | Daily | Validates the DMSI Advanced API plugin license against the EDD license server |
Reliable Cron Execution #
WP-Cron only fires when the WordPress site receives an HTTP visit. On low-traffic sites, cron jobs — including webhook delivery retries — may be delayed.
For reliable background job execution, install the Action Scheduler plugin. When Action Scheduler is present, the plugin uses it for webhook delivery instead of WP-Cron, providing guaranteed retry scheduling independent of site traffic.