Skip to content
This repository was archived by the owner on Mar 13, 2025. It is now read-only.
This repository was archived by the owner on Mar 13, 2025. It is now read-only.

RCRM Job candidate Rejected Status Integration loop #142

@sandhiyakavi

Description

@sandhiyakavi
Collaborator

Inifinite loop scenario happening with the Zap: 5 PROD - JOBCANDIDATE Update All Status RCRM to TaaS and 4-PROD-JOBCANDIDATE-Status-to-Rcrm

Activity

maxceem

maxceem commented on Apr 8, 2021

@maxceem
Contributor

References:

Suggested fix:

As have been discussed on Slack we would add a new status topcoder-rejected to indicate that candidate has been rejected in RCRM.

self-assigned this
on Apr 8, 2021
added and removed on Apr 9, 2021
maxceem

maxceem commented on Apr 9, 2021

@maxceem
Contributor

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:

  • should post to Zapier if status is changed to “rejected”
  • should post to Zapier if status is changed to “shortlist”
  • should not post to Zapier if status was already “rejected” and updated to “rejected”
  • should not post to Zapier if status was already “shortlist” and updated to “shortlist”
  • should not post to Zapier if status is changed to “interview” or another one (not “rejected” or “shortlist”)
  • should not post to Zapier if status is changed to "topcoder-rejected" (not "rejected" or "shortlist")

Though it appears that there was a second part of issue:

  • when rejecting JC from RCRM we want the JC status to be Topcoder Rejected (topcoder-rejected)
  • while when rejecting JS from TaaS we want the JS status to be Client Rejected (rejected)

For this purpose, we added support for a new status topcoder-rejected to Job Candidates.

DEV PRs

PROD PRs

added this to the v1.5.3.1 Hotfix milestone on Apr 9, 2021
SathyaJayabal

SathyaJayabal commented on Apr 9, 2021

@SathyaJayabal
Collaborator

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.

SathyaJayabal

SathyaJayabal commented on Apr 9, 2021

@SathyaJayabal
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @maxceem@sandhiyakavi@SathyaJayabal

      Issue actions

        RCRM Job candidate Rejected Status Integration loop · Issue #142 · topcoder-archive/topcoder-platform-taas-app