EspoCRM background jobs: cron vs daemon and parallel processing
Setting up EspoCRM job processing that keeps up: crontab versus daemon, parallel processes, job parameters, running jobs from the CLI and checking scheduled job logs.

Day-two work on a running EspoCRM: background jobs, performance and indexes, logs, troubleshooting email and scheduled jobs, rebuilds, backups and admin recovery.
Setting up EspoCRM job processing that keeps up: crontab versus daemon, parallel processes, job parameters, running jobs from the CLI and checking scheduled job logs.
Speeding up a growing EspoCRM: server choices, MariaDB buffer pool and sort buffers, database choice for heavy filters, and list view and report habits that slow it down.
Creating indexes for EspoCRM fields used in default sorting, filters and reports: defining indexes in entity metadata, rebuilding and checking which queries need them.
Finding what went wrong in EspoCRM: log location and levels, SQL and failed-SQL logging, the admin UI app log, debug mode for diagnosis and keeping traces out of production.
When emails stop fetching or workflows do not fire: checking cron or the daemon, the web server user, scheduled job status, stuck jobs and parallel processing settings.
Diagnosing EspoCRM inboxes that do not update: cron, IMAP settings, OAuth for Gmail and Outlook, fetch delays and how linking of incoming email to records works.
Using EspoCRM's rebuild tools safely: clear cache, rebuild from the admin panel or CLI, hard rebuild to clean columns and collations, and taking a backup first.
Backing up a self-hosted EspoCRM: the backup script, manual file and database dumps, Docker volume backups, restore steps and testing restores regularly.
Getting back into EspoCRM when the admin password is lost: set-password from the CLI, re-enabling admin password recovery, and keeping a break-glass admin account.
Resolving two common database errors in heavily customized EspoCRM: too many joined tables in list views and reports, and row size limits from many text fields.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.