-
Notifications
You must be signed in to change notification settings - Fork 24
RCRM Job candidate Rejected Status Integration loop #142
Comments
References:
Suggested fix:As have been discussed on Slack we would add a new status |
We found out the root cause of looping and fixed it via topcoder-platform/taas-es-processor#33. The general idea of the fix, we should not post to Zapier to update status, if status was not really updated. Added the next unit tests which verify this logic:
Though it appears that there was a second part of issue:
For this purpose, we added support for a new status DEV PRs
PROD PRs |
Verified the status updates between RCRM and TaaS App after the addition of the new status. The syncing of the statuses between the apps is working fine on Dev. |
Verified the status updates between RCRM and TaaS App after the addition of the new status. The syncing of the statuses between the apps is working fine on Prod. |
Inifinite loop scenario happening with the Zap: 5 PROD - JOBCANDIDATE Update All Status RCRM to TaaS and 4-PROD-JOBCANDIDATE-Status-to-Rcrm
The text was updated successfully, but these errors were encountered: