Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Content jobs

How the kernel runs large content operations in the background - removes, copies, moves, hides, sections, states, locations, package installs and audit exports - with their progress page, command, cronjob part, settings…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/creators/app-creators/content-jobs.md

On this page

Content jobs

This page is for application creators who work with large subtrees. The kernel turns large content operations into content jobs that run in the background in batches, with a progress page, instead of one long request (Content jobs).

The job queue dashboard, which lists the content jobs and their state
The job queue dashboard, which lists the content jobs and their state

Contents

  1. What becomes a job
  2. The command
  3. Settings
  4. Reliability
  5. Using jobs from an application

What becomes a job

Remove, copy, move, hide, reveal, section assignment, subtree states, adding and removing locations, package installs and audit exports (JobTypes[]). Editors choose "now" or "in the background"; from SynchronousLimit items the background is preselected, above NowLimit it is the only choice. Progress: content/job/<id>; list: content/jobs.

The command

php bin/php/expcontentjob.php list [--all]
php bin/php/expcontentjob.php show <id>
php bin/php/expcontentjob.php remove <node>[,<node>...] [--trash|--delete] [--background]
php bin/php/expcontentjob.php copy <source> <new parent> [--background]
php bin/php/expcontentjob.php move <node> <new parent>
php bin/php/expcontentjob.php run <id> | resume <id> | cancel <id>

Also php bin/php/console exp:expcontentjob ....

Settings

content.ini [ContentJobSettings]:

SettingDefaultMeaning
SynchronousLimit50from this many items the background is preselected
NowLimit1000above this many "now" is not offered
BatchSize50nodes per batch, one transaction each
BatchPause0milliseconds between batches (100 to 200 on SQLite)
QueuedGrace60seconds before the cron part starts a job nobody started
MaxAttempts5worker starts without progress before the job fails
KeepDays30finished jobs are removed after this many days

Reliability

The contentjobs cron part (in the frequent group) starts jobs whose worker never started and resumes jobs whose worker died, so a job is not lost when the web server cannot start a worker. On a cluster, the job directory must be shared.

Using jobs from an application

  • For large operations on content, call the command (or its service) instead of looping over thousands of nodes in a request.
  • For your own background work, use the job queue expqueue, which is separate from content jobs and built for application jobs (Queues with expqueue).
  • Give supervisors content/jobs to see every user's jobs.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x