/
After adding the "Push to Salesforce" post-function to the workflow, the connector fails to trigger the post-function and fails to update Salesforce following the Jira status transition.

After adding the "Push to Salesforce" post-function to the workflow, the connector fails to trigger the post-function and fails to update Salesforce following the Jira status transition.

 Problem

After adding the “Push to Salesforce” post-function within a transition in the Jira workflow, the connector is not pushing the updates to Salesforce after the Jira status transition.

 Solution

To ensure the post-function works as expected, it needs to be placed at the end of all post-functions of the transition, as shown in the image below.

image-20240515-190041.png

If the post-function is not at the end of the list, simply click on the down arrow located to the right of the push to Salesforce post-function. This action will relocate it to the bottom of the post-functions list.

image-20240515-185928.png

If the issue persists after following this troubleshooting recommendation, please get in touch with us through the support portal and submit a support ticket. A support engineer will assist you with resolving this matter.

Please include a screenshot of the added post-function in the ticket.

Related content

Configuring workflow post functions in Jira
Configuring workflow post functions in Jira
More like this
When a Salesforce Record is opened, an [Invalid string length] component error appears.
When a Salesforce Record is opened, an [Invalid string length] component error appears.
Read with this
[Includes] Delayed Execution
[Includes] Delayed Execution
More like this
Permission errors while executing post-functions
Permission errors while executing post-functions
More like this
Why does my association not auto-push back to other associated Salesforce Objects after pulling to Jira
Why does my association not auto-push back to other associated Salesforce Objects after pulling to Jira
More like this