Expected entity does not exist - 02419316

Forum for users and developers of Bullhorn's API service.

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
Kazemi
User
Posts: 41
Joined: Tue Oct 11, 2016 1:26 pm

Expected entity does not exist - 02419316

Post by Kazemi » Mon Jan 30, 2017 8:43 pm

We're finding some entities don't exist when we search for them, particularly after seeing an update for the entity from the subscription endpoint.

For example, after seeing an "Updated Candidate" event from the subscription endpoint, we query Bullhorn (verified using both /search and /query) for the entity's values using the candidate's ID. The response is an empty list.

We thought this might be because the entity was deleted, but both /search and /query return deleted entities (this was verified against a sandbox account). This has come up using multiple accounts, across multiple entities, every day for the last week or so.

We're stuck. Why might we not be seeing these entities?

ColinC
User
Posts: 67
Joined: Fri Apr 08, 2016 4:54 pm

Re: Expected entity does not exist

Post by ColinC » Tue Jan 31, 2017 10:21 am

Hello Kazemi,

Typically when REST returns an empty set when the search criteria is slightly off. Could you give me an example rest call of everything /search and beyond for candidates? I'd like to take a look.
ex. /search/Candidate?query=isDeleted:0


Thank you,
Colin
Colin Coffman
Enterprise Support Analyst
B U L L H O R N
Staffing and Recruiting Software, On Target, On Demand
617-478-9126 (US Support)
+44 800 032 2848 ext. 9131 (UK Support)

Kazemi
User
Posts: 41
Joined: Tue Oct 11, 2016 1:26 pm

Re: Expected entity does not exist - 02419316

Post by Kazemi » Fri Feb 03, 2017 7:35 pm

Hi Colin,

Here's the exact url we're formulating:

https://rest0.bullhornstaffing.com/rest ... ,candidate(id, firstName, lastName),dateAdded,dateClientEffective,dateLastModified,dateEffective,dateBegin,dateEnd,durationWeeks,employmentType,terminationReason,status,overtimeRate,clientOvertimeRate,daysGuaranteed,workWeekStart,statementClientContact(id, firstName, lastName),taxState,hoursPerDay,otherHourlyFee,billingClientContact(id, firstName, lastName),clientCorporation(id, name),clientContact(id, firstName, lastName, name, email, mobile, phone),clientBillRate,quitJob,flatFee,referralFeeType,reportTo,salaryUnit,daysProRated,employeeType,salary,payRate,jobSubmission(id)

It's a long list of fields, but this query works almost every time for other Placements (except: in the case we discuss here). The only change is the lookup id in the query.

It's a little difficult to understand why it's not working. FWIW, we keep track of changes via the /subscriptions endpoint, and haven't seen any "DELETED" events for this particular entity. But even if we did, our limited testing with a sandbox account showed the API returns deleted entities by default. Is it possible the subscription endpoint is dropping events and the API has been configured not to return deleted entities? Just a hypothesis!

ColinC
User
Posts: 67
Joined: Fri Apr 08, 2016 4:54 pm

Re: Expected entity does not exist - 02419316

Post by ColinC » Mon Feb 06, 2017 5:45 pm

Hi Kazemi,

It certainly is possible, though extremely rare, that a sub might drop a subscription. Typically around .0001% of the time on heavily used systems. That said something else could have failed to process the event for any number of local reasons then skipped.

Placements are also hard deletes so once they're gone, they're gone in app / the back end of our system. Candidates, for example are soft deletes and have the isDeleted field that is updated and can still be called through the API. Hard Deletes cannot be returned once gone.

Without looking at a log monitoring all incoming information it would be very difficult to tell what happened. DataMart/DataMirror have requestStatus tables that failed requests go into and will have a why. If you're using one of those or have something similar there could be a reason there. So, yes, it is possible that your hypothesis is correct while looking at placements.

Let me know if you have any further questions.

Colin
Colin Coffman
Enterprise Support Analyst
B U L L H O R N
Staffing and Recruiting Software, On Target, On Demand
617-478-9126 (US Support)
+44 800 032 2848 ext. 9131 (UK Support)

Kazemi
User
Posts: 41
Joined: Tue Oct 11, 2016 1:26 pm

Re: Expected entity does not exist - 02419316

Post by Kazemi » Mon Feb 06, 2017 9:41 pm

Thanks Colin,

We're seeing this happen at a rate anywhere from ~0.1-10% (yes, 10%!) depending on the agency, which is ~1,000-100,000x more than .0001%! Something is off - can we investigate this further, maybe offline?

ColinC
User
Posts: 67
Joined: Fri Apr 08, 2016 4:54 pm

Re: Expected entity does not exist - 02419316

Post by ColinC » Tue Feb 07, 2017 12:21 pm

Hi Kazemi,

If you are a support contact or are able to get a support contact to call in or submit a ticket on your behalf and mark you as a point of contact we can connect through that. I may not be the person who assists you as we have many analysts well versed in this.

From there better communication can be had.

Kind regards,
Colin
Colin Coffman
Enterprise Support Analyst
B U L L H O R N
Staffing and Recruiting Software, On Target, On Demand
617-478-9126 (US Support)
+44 800 032 2848 ext. 9131 (UK Support)

Post Reply