Job execution storage

What is a job execution storage?

Whenever a job is launched, whether is starts immediately or not, an execution is stored for it.

The execution are stored to allow you to keep an eye on what is happening.

This persistence is on the responsibility of the job execution storage.

How do I store my Job Execution?

You should never be forced to store JobExecution yourself.

This is the role of the JobLauncher job to store it whenever it is required (usually at the beginning and the end of the job execution).

How can I retrieve a Job Execution afterwards?

Every storage implements JobExecutionStorageInterface that has a method called retrieve. Use this method to retrieve one execution using job name and execution id.

Depending on which storage you decided to use, you may also be able to:

Warning

Sometimes the storage may implement these interfaces, but due to the way executions are stored, it might not be recommended heavily rely on these extra methods.

What types of storages exists?

Built-in storages:

Storages from bridges:

Storages for testing purpose: