Date: Fri, 29 Mar 2024 09:39:07 +0000 (UTC) Message-ID: <203419816.12689.1711705147265@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12688_333506751.1711705147265" ------=_Part_12688_333506751.1711705147265 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Can a job call a database procedure or successor job as a method of hand= ling errors?
Error states within job chains are assigned to job and it is up to you t= o implement a job for error handling. The JobScheduler can be configured to= send mails with an attached log file in the event of errors when a specifi= c error handling job is not used.
The use of successor jobs in case of errors can be configured using the&=
nbsp;on_exit_code
attribute:
<= job stop_on_error=3D"no"> ... <commands on_exit_code=3D"error"> <start_job job=3D"my_error_handler"><params/></start= _job> </commands> </job>
This configuration lets the job start a successor in case of an error th=
at is signaled by an exit code that is not 0. In addition, this example cau=
ses the job to continue in case of errors (<job stop_on_error=3D...>), i.e. the normal behavior for jobs that are not in job chains - to stop=
the job in case of errors - does not apply. Individual exit codes and rang=
es of exit codes can be specified for the
on_exit_code
attribu=
te.