Searching be external_id doesn't return a result about zendesk_api_client_rb

[jwswj]

@maxkwallace The delay does, and can be anywhere between 1-10mins due to the way our search indexing currently works. We have a project to rebuild our indexer pipeline, however it's a big project so it won't drop for a while. What's your use case, maybe there is a workaround...

[jwswj]

I've raised the issue with the search team so hopefully it can be mentioned on that page @maxkwallace.

[keithpitt]

I've also tweeted about this issue: https://twitter.com/zendeskdevteam/status/311986195473260544

[jwswj]

This is due to our search index having a bit of a delay. The delay varies, but after 10mins it's normally caught up.

Do you need to use search? The zendesk_ticket object will have the ticket ID after save. Then using the ticket ID will always result in the most up-to-date details. Eg.

found_ticket = ::ZendeskAPI::Ticket.find(ZENDESK_CLIENT, :id => zendesk_ticket.id)

[keithpitt]

This is a simplified example, but the two operations are usually separated by different background jobs in our system.

I'm storing a cache at the moment of our internal id's and the zendesk ticket id's. Looking to the cache before trying to do the search. This should work for the most part - but I was just curious because I would have thought that searching by external-id's would have been fast.

[jwswj]

@devarispbrown @steved555 Any plans for something like found_ticket = ZendeskAPI::Ticket.find(ZENDESK_CLIENT, :external_id => external_id)

[devarispbrown]

Not at the moment, but I can add it to the dev backlog.

On Tue, Mar 19, 2013 at 8:17 PM, Jason Smale [email protected]:

@devarispbrown https://github.com/devarispbrown @steved555https://github.com/steved555Any plans for something like found_ticket
= ZendeskAPI::Ticket.find(ZENDESK_CLIENT, :external_id => external_id)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/80#issuecomment-15156377
.

[maxkwallace]

@jwswj does the 10 minute delay apply to searching Users?

[maxkwallace]

@jwswj thanks for the reply! I can work around this using the existing API, but this delay should definitely definitely definitely be reflected in the docs (e.g. https://developer.zendesk.com/rest_api/docs/core/search). It's very frustrating to try to design around limitations like this when they're buried in GitHub issues.