Date: Fri, 29 Mar 2024 14:57:33 +0000 (UTC) Message-ID: <547589649.11.1711724253329@b0c175436f18> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10_1668769802.1711724253329" ------=_Part_10_1668769802.1711724253329 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There is a fundamental difference between Jira Server/Data Cente=
r and Jira Cloud: In Jira Cloud, post functions of apps a=
re executed asynchronously as a 'background job'.=
This means a post function will be executed after the transition ha=
s been completed on Jira Cloud.
Note the following behaviors of the asynchronous execution:
If you are using multiple post functions, there is no guaranteed order i= n which they are performed. They might be executed in a different order fro= m the one you set up in Jira's workflow configuration. Therefore, you canno= t rely on any result of a previous post function. Also, the order in which = the post functions are executed might be different every time the transitio= n is performed.
If a post function encounters a problem (due to misconfiguration or the = current data of a Jira issue), the transition (and all other post functions= ) will be performed regardless of the problem.
The result of a post function might not be visible immediately in the br= owser.
There are no error messages displayed to the user.