Most of the things done in Keboola Connection run as background, asynchronous jobs. For an overview of all jobs, running and finished, go to the Jobs section:
All jobs are logged and their tracked history is virtually unlimited. Click on a job to see details on
Using the search box and advanced patterns you can easily find job based on various parameters.
|User who created the job||
|(Docker) Component name||
(possible values are
|Exclude some results||
(Note the minus sign before the query)
|Open ended time query||
Show jobs after 21st June 2018.
|Long running non-successful orchestrations (more than 2 hours)||
|Orchestrations which ended with warning||
|Failed jobs from Docker component HTTP extractor||
|Jobs from either HTTP extractor or Google Sheets writer||
|All non-successful jobs from either HTTP or Google Sheets writer||
For more technical information about background jobs, see our Developers documentation.
Jobs are either run manually from any configuration or automatically by the Orchestrator at a scheduled time. In either case, the typical life time of a job has the following states:
waiting –> processing –> success/error
Until a job is finished (i.e., it is waiting or processing), it can be terminated:
Note that a job is not terminated immediately upon clicking the Terminate button. Its termination usually takes a few seconds.
In some cases, a job can have child jobs. They are identified by having their
RunId delimited with
a dot — e.g.,
347371952.3473719650. In this case, the job
3473719650 run is in fact a child
347371952. Terminating the parent job will automatically terminate the child job too.
Terminating the child job will probably cause the parent to terminate or fail.
When a job is run, it is always put in the waiting state to wait for our infrastructure — worker to start executing it. This usually takes anywhere from several seconds to a couple of minutes at most.
There is one more reason for a job to be in the waiting state: project parallelism limits. Either the same configuration of the same component is already being executed, or the overall limit of concurrently running jobs within a project was exceeded. That means that a job will be in the waiting state under the following conditions:
Not only we record all jobs executed in your Keboola Connection project, we also record all data that was uploaded into it. Go to Storage and click the Jobs tab:
When you click an importTable job, you’ll see the Storage job detail:
Clicking File ID will take you to the Files section in Storage, where all data pushed into your Keboola Connection project is stored. You can download the data and import it into other tables, or you can revert to an older table version.