Service Issues

Report any Haven OnDemand API service issues to the development team here. Before submitting your issue and for issue status definitions, be sure to read this page.
Search the Dev Community
Showing results for 
Search instead for 
Do you mean 
Post a Message
0 Likes
Status:
Not an Issue

Speech recognition error 5000

Status:
Not an Issue
by krishnaguy New Member on ‎03-12-2016 04:17

I am trying to call the speech to text services via Python, but get a "Backend request failed" error. However I do get results when I upload the file via the "Try it" interface.

 

My code snippet below:

 

import requests

r = requests.post('https://api.havenondemand.com/1/api/async/recognizespeech/v1', data = {'apikey':'KEY', 'language':'en-US-tel', 'file':'file_name_with_full_path'})

 

and the error:

 

{u'actions': [{u'action': u'recognizespeech',
   u'errors': [{u'error': 5000, u'reason': u'Backend request failed'}],
   u'status': u'failed',
   u'version': u'v1'}],
 u'jobID': u'JOB-ID',
 u'status': u'failed'}

 

I have attached the sample wav file that I was using as well. 

Status:
Not an Issue

Hi Krishnaguy,


Thanks for getting back to us with the update.


Do let us know if you need anything further.

 

Chris
Haven OnDemand team

0 Likes
Status:
Not an Issue

I'm using the entity extraction API and finding that 'Michael Roe' is extracted from my uploaded document. But in the uploaded document two people names is there Ulrich Bernier and Michael Roe. So How can i get the both names Ulrich Bernier and Michael Roe.

Status:
Not an Issue
0 Likes
Status:
Not an Issue

Patents QueryTextIndex by reference

Status:
Not an Issue
by Gordo Level 4 on ‎03-23-2015 09:22

If I do the following query:

 

curl "https://api.idolondemand.com/1/api/sync/querytextindex/v1?text=DREALL&indexes=patents&summary=concept&apikey=<APIKEY>"

 I get back some results:

 

 "documents": [
    {
      "reference": "http://www.google.com/patents/USD07640597",
      "weight": 85.35,
      "links": [],
      "index": "patents",
      "title": "Image display device",
.....

 If i then try and query for this reference:

 

curl "https://api.idolondemand.com/1/api/sync/querytextindex/v1?reference=http%3A%2F%2Fwww.google.com%2Fpatents%2FUSD07640597&indexes=patents&apikey=<APIKEY>"

 I get the following:

 

{
  "error": 5013,
  "reason": "Job actions failed",
  "actions": [
    {
      "errors": [
        {
          "error": 5013,
          "reason": "Reference does not exist"
        }
      ],
      "status": "failed",
      "action": "querytextindex",
      "version": "v1"
    }
  ],
  "status": "failed"
}

 Is this a bug or am I misunderstanding something?

Status:
Not an Issue

Gordo,

 

Reference is his case is a reference to a file uploaded via the storeobject API rather than an index reference.

 

If you are trying to retrieve the given document you will need to use getcontent & the index_reference parameter, or if you would like to do findsimilar to find similar documents, you will again need to pass the reference as index_reference rather than reference.

 

Regards


Chris

IDOL OnDemand team

0 Likes
Status:
Not an Issue

Why does it say Index Name invalid for some of the Requests - AddtoTextIndex

Status:
Not an Issue
by logontokartik Level 1 on ‎07-07-2014 02:21 - last edited on ‎07-07-2014 08:04 by Level 7

Hi,

For some requests its successful, but for some of the addtotextindex requests it says Index name invalid and returns 8002. Why does it do that? Below is one of the requests that failed.

 

https://api.idolondemand.com/1/api/sync/addtotextindex/v1?index=sfdc_idol_index&json=%7B%22documents... Method=GET]

 

 

{
  "error": 8002,
  "reason": "Job actions failed",
  "actions": [
    {
      "status": "failed",
      "action": "addtotextindex",
      "version": "v1",
      "errors": [
        {
          "error": 8002,
          "reason": "Index name invalid"
        }
      ]
    }
  ],
  "jobID": "usw3p_d564bc60-ee13-406a-a81c-c704aee704e0",
  "status": "failed"
}
Status:
Not an Issue
The reason this specific request fails is due to an invalid index name. The api-key is associated with a different index name as specified. I.e. the api-key and the current request are using sfdc_idol_index whilst the api-key is associaed with an index created called – kindex9
0 Likes
Status:
Not an Issue

I submitted an async "Add To Text Index". The response was the job was queued. But, I get an error when getting the job status. This happens all the time. Any idea what is wrong?

 

Oct 07, 2014 12:46:06 PM com.sun.jersey.api.client.filter.LoggingFilter log
INFO: 3 * Client out-bound request
3 > GET https://api.idolondemand.com/1/job/status/usw3p_69d126de-d9e3-4142-a117-eed4d5f07713?apikey=<omitted...
3 > Accept: application/json

Oct 07, 2014 12:46:06 PM com.sun.jersey.api.client.filter.LoggingFilter log
INFO: 3 * Client in-bound response
3 < 500
3 < ETag: "-170317185"
3 < x-content-type-options: nosniff
3 < Access-Control-Allow-Headers: Content-Type
3 < Access-Control-Allow-Origin: *
3 < Date: Tue, 07 Oct 2014 16:46:06 GMT
3 < Content-Length: 106
3 < Access-Control-Allow-Methods: GET,PUT,POST,DELETE
3 < Connection: keep-alive
3 < Content-Type: application/json; charset=utf-8
3 < Server: nginx/1.6.1
3 <
{
  "message": "Unknown",
  "detail": {
    "error": 1000,
    "reason": "Unable to validate quotas"
  }
}

Status:
Not an Issue
0 Likes
Status:
Not an Issue

Error - Backend job failed

Status:
Not an Issue
by Yogas Level 1 on ‎11-19-2014 06:59

I was working with "Find Similar" API , I'm giving source as csv file , but I''m getting below error , help me to know what's wrong with the input or any workaround . 

 

{
"error": 5000,
"reason": "Job actions failed",
"actions": [
{
"errors": [
{
"error": 5000,
"reason": "Backend request failed",
"detail": "ERROR"
}
],
"status": "failed",
"action": "findsimilar",
"version": "v1"
}
],
"status": "failed"
}

Status:
Not an Issue
0 Likes
Status:
Not an Issue

500 - Backend Request Failed

Status:
Not an Issue
by justing Level 2 on ‎12-05-2015 12:43

Hi,

 

While attempting to use the view document API, I've recently started hitting a 500 internal error - here's the JSON

 

{
    "error": 5000,
    "reason": "Job actions failed",
    "actions": [
        {
            "errors": [
                {
                    "error": 5000,
                    "reason": "Backend request failed",
                    "detail": "Worker request failed"
                }
            ],
            "status": "failed",
            "action": "viewdocument",
            "version": "v1"
        }
    ],
    "status": "failed"
}

Is this a configuration issue on our part? 

Social Media
† The opinions expressed above are the personal opinions of the authors, not of HPE. By using this site, you accept the Terms of Use and Rules of Participation