Krom Automation’s settings live at Krom Automation > Settings in your WordPress admin. The settings page has four tabs: Logging and Cleanup, Performance, License Management, and Debug and Tools. There’s also a separate AI Settings section for configuring AI provider API keys.

This page documents every setting, what it controls, and when to change it.

Tab 1: Logging and Cleanup #

These settings control whether Krom Automation records execution data and how long it keeps that data.

Setting	Type	Description
Enable Logging	Toggle	When enabled, Krom Automation records every workflow execution to the database, including step-by-step results, input data, and output data.
Auto-Cleanup	Toggle	When enabled, Krom Automation runs a daily background job that deletes log entries older than the Retention Period.
Retention Period	Number	How many days to keep execution logs. Accepts values from 1 to 365. After this period, old logs are deleted by the daily cleanup job.
Debug Mode	Toggle	When enabled, Krom Automation records additional detail in logs, including verbose error information and internal execution data.

Recommended logging configuration

For most sites: Leave Enable Logging on, Auto-Cleanup on, and Retention Period at 30 days. This gives you a month of execution history for troubleshooting without accumulating excessive database rows.

For high-traffic sites with many active workflows: Reduce the Retention Period to 7 or 14 days. A busy site with dozens of active workflows can generate thousands of log rows per day. Shorter retention keeps the database table size manageable.

When troubleshooting a specific issue: Enable Debug Mode temporarily. Check the logs for the additional detail, find the root cause, then disable Debug Mode again. Debug Mode increases the size and volume of log data significantly and should not be left on permanently.

If you want to turn off logging entirely: Disable Enable Logging. No execution data will be written to the database. The Logs and Analytics pages will show no data. Only do this if database storage is a concern and you don’t need execution history.

How the daily cleanup works

When Auto-Cleanup is enabled, Krom Automation registers a WordPress Cron job called krom-automation_daily_cleanup. This job runs once per day and deletes all log entries older than your configured Retention Period.

The cleanup runs in the background and does not affect your site’s front end. If you need to free up database space immediately without waiting for the daily cron, use the Manual Logs Cleanup tool in the Debug and Tools tab.

Tab 2: Performance #

Setting	Type	Description
Max Execution Time	Number	The maximum number of seconds a single workflow step is allowed to run before Krom Automation times it out. Accepts values from 30 to 600 seconds. Default is 30 seconds.
Worker Mode	Select	Controls how Krom Automation processes background jobs. Standard mode uses Action Scheduler (the default). High-performance Worker Mode is available in Krom Automation Pro.

Choosing a Max Execution Time value

The default of 30 seconds is appropriate for the vast majority of workflows. Most steps complete in under a second.

Increase Max Execution Time if you’re using the HTTP Request action to call a slow external API that sometimes takes longer than 30 seconds to respond. Set it to a value slightly higher than the slowest expected response time from your external service.

Do not set it excessively high (above 120 seconds) without a specific reason. Very long timeouts can cause delayed jobs to pile up if many executions are waiting on a slow step, which puts pressure on the Action Scheduler queue.

Worker Mode

Standard mode (the default) uses Action Scheduler to process all workflow executions as background jobs. This works reliably on all WordPress hosting environments.

High-performance Worker Mode is a Krom Automation Pro feature designed for sites with very high workflow execution volumes. It processes jobs more efficiently under load. If you’re running thousands of executions per day and seeing delays, upgrading to Pro and enabling Worker Mode is the solution.

Tab 3: License Management #

Setting	Description
License Status	Displays whether your site is running Krom Automation Free or has an active Pro license.
License Key	The field where you enter your Krom Automation Pro license key after purchase.

To activate Pro, enter your license key and click Save. Krom Automation connects to the wpRigel license server, validates the key, and unlocks Pro features immediately.

To deactivate Pro (for example, to move the license to a different site), use the Deactivate button that appears when a Pro license is active.

See How to Install and Activate Krom Automation Pro for the full activation walkthrough.

Tab 4: Debug and Tools #

Tool	Description
Manual Logs Cleanup	Immediately deletes all execution logs older than the configured Retention Period. Runs right now rather than waiting for the next scheduled daily cleanup.
Reset Plugin Data	Wipes all Krom Automation data from the database, including all workflows, execution logs, analytics, and settings. This is a developer tool for resetting a site to a clean state.

When to use Manual Logs Cleanup

Use this when your database is under storage pressure and you need to free up space right now. It deletes everything older than your Retention Period immediately, without waiting for the nightly cron.

It does not delete logs within the retention window. If you want to clear everything, temporarily set the Retention Period to 1 day, run Manual Logs Cleanup, then restore your preferred retention setting.

Reset Plugin Data: read this before using it

Reset Plugin Data is irreversible. It permanently deletes:

• All workflows (active and paused)
• All execution logs
• All analytics data
• All settings

It does not uninstall the plugin or remove Krom Automation’s database tables. After a reset, Krom Automation is in the same state as a fresh activation with no workflows configured.

Only use this on a development or staging site, or when you explicitly need to start from scratch. There is no undo.

AI Settings #

The AI Settings section appears separately from the four tabs. It’s where you configure API keys for Krom Automation’s three AI actions.

Provider	Models	Where to get your key
OpenAI	GPT-4o Mini, GPT-4o	platform.openai.com
Google Gemini	Gemini 2.0 Flash, Gemini 2.5 Flash Preview, Gemini 2.5 Pro Preview	aistudio.google.com
Groq	Llama 3.3 70B, Llama 3.1 8B, Mixtral 8x7B	console.groq.com

Enter your API key for any one provider and save. Krom Automation will use that provider for all AI actions when you select the Auto model. You can configure multiple providers if you want to choose specific models in individual workflows.

API keys are stored in your WordPress database. They are never exposed in the workflow editor, execution logs, or any front-end output.

Background scheduled tasks #

Krom Automation registers two recurring background tasks using WordPress Cron. You can inspect these in Tools > Scheduled Actions if you have a cron management plugin like WP Crontrol installed.

Task	Frequency	What it does
krom-automation_daily_cleanup	Daily	Deletes execution logs older than the configured Retention Period
krom-automation_hourly_health_check	Hourly	Checks for stuck or long-running executions and flags them in the logs

Both tasks run silently in the background. If your host has disabled WordPress Cron, neither task will run. Contact your host or configure a real server cron to call wp-cron.php on a schedule if WP-Cron isn’t available.