Discrepancy in eQuest Posting End Date. — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Discrepancy in eQuest Posting End Date.

in Recruiting, Opportunity Marketplace 1 comment

Summary:

Hello,

We are experiencing an issue where job requisitions configured with "Automatically fill Job Requisition" set to Yes that are being automatically filled upon hiring, the eQuest posting end date is set to one year in the future with the status "Posting removal Initiated." Despite this, the posting still appears on LinkedIn and other job boards.

However, when we manually fill the job requisition using Actions → Fill Job Requisition, the eQuest posting end date is set to the current system date, which is the expected behavior.

We also reached out to eQuest, and they confirmed that for these requisitions, they did not receive any API call from Oracle to close the postings.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!