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:
Completed

Having posted a largish (200Mb file) to the recogniser service using the following:

 

curl "https://api.idolondemand.com/1/api/async/recognizespeech/v1" -X POST -H Content-Type:multipart/form-data; --insecure -o response.json -F apikey=<APIKEY> -F language=enuk -F file=@trimmed.mp4

 

I check the status

 

curl "https://api.idolondemand.com/1/job/status/usw3p_4b284786-2b80-475c-8674-6f9c29422cb7" -X POST --insecure -F apikey=<APIKEY>
{
"actions": [
{
"errors": [
{
"error": 5000,
"reason": "Backend request failed"
}
],
"status": "in progress",
"action": "recognizespeech",
"version": "v1"
}
],
"jobID": "usw3p_4b284786-2b80-475c-8674-6f9c29422cb7",
"status": "queued"
}

 

Why am I getting this:

 

"error": 5000,
"reason": "Backend request failed"

 

Is this indicative of a problem or should I disregard this and assume that my request is still queued?

 

Thanks

 

Gordon

 

Status:
Completed
0 Likes
Status:
Completed

Hello,

I send a text less than 100 chars (~10 words) and the API gives the following response (it doesn't recognize the language):

 

{
  "language": "unknown",
  "language_iso639_2b": "und",
  "encoding": "UTF8",
  "unicode_scripts": [
    "Basic Latin"
  ]
}

 

I decided to put more text ~300 chars (~40 words) and now it give this:

 

{
  "error": 5003,
  "reason": "Job actions failed",
  "actions": [
    {
      "status": "failed",
      "action": "identifylanguage",
      "version": "v1",
      "errors": [
        {
          "error": 5003,
          "reason": "Job result was invalid"
        }
      ]
    }
  ],
  "jobID": "usw1p_2f96eff6-7bc2-40cc-b991-1975d09b375d",
  "status": "failed"
}
Status:
Completed
This should be resolved. Let us know if you are still having an issue.
0 Likes
Status:
Completed

Below is resulting output for my latest test converting http://www.seancaldwell.com/audio/corporate.mp3. Here is another file which failed before - https://www.dropbox.com/s/ky7ji6dcu3uyenf/Test-Speech-Recognition.mp4?dl=0

 

What am I doing wrong?

 

Thx,

Rtko

 

 

Error.jpg

 
 
Status:
Completed

The Try It page now supports Asyncronous mode API calls to prevent timeouts on the processing of large files.

 

Please give it a try and let us know if you have any further feedback.

 

Regards


Chris

IDOL OnDemand team

0 Likes
Status:
Completed

Not able to delete or query a text index

Status:
Completed
by hdas New Member on ‎07-12-2014 03:34

This is very weird. The text index is not working as expected. It seems to have a lot of bugs.

  1. Once the text index is created, it can not be deleted
  2. Even it can not be delected from IDOL on demand's UI interface
  3. API also can not delete it saying "Job action failed"
  4. Can not query anything from text index, again same error "Job action failed".

This is now very urgent. Please fix these issues.

Status:
Completed

Hi hdas,

 

We introduce a number of improvements in our release last week to improve the resilience of the createtextindex and deletetextindex APIs, as well as making them quicker to execute.  This should resolve your issue.


Do let us know if you have any further questions, issues or feedback.


Regards


Chris

0 Likes
Status:
Completed

RecognizeSpeech Error

Status:
Completed
by Gordo Level 4 on ‎04-27-2015 04:11

I uploaded a WMA file to the service for transcription :

curl "https://api.idolondemand.com/1/api/async/recognizespeech/v1" -X POST -H Content-Type:multipart/form-data; --insecure -F apikey=<APIKEY> -F language=enuk -F file=@target_london_811_0186.WMA


{
  "jobID": "usw3p_c78ce6e7-5e95-4fdc-afab-23ef3c7408f2"
}

 After a wihle I check the status:

 

curl "https://api.idolondemand.com/1/job/status/usw3p_c78ce6e7-5e95-4fdc-afab-23ef3c7408f2" --insecure -F apikey=<APIKEY>

 The response

 

 

{
  "actions": [
    {
      "errors": [
        {
          "error": 5007,
          "reason": "Key Management Service Error"
        }
      ],
      "status": "failed",
      "action": "recognizespeech",
      "version": "v1"
    }
  ],
  "jobID": "usw3p_c78ce6e7-5e95-4fdc-afab-23ef3c7408f2",
  "status": "failed"
}

 Why does this happen?

 

Status:
Completed
0 Likes
Status:
Completed

Error 1000 "Unknown" Sentiment Analysis

Status:
Completed
by Dave New Member on ‎10-28-2014 09:33

I'm doing a rapid fire of about ~1000 API calls to the sentiment analysis API and getting the majority of them back as Error 1000 "Unknown".  Not very helpful... is this specific to the sentiment analysis API or some kind of generic error (that could use a better message) about reaching a rate limit quota?  Is the Sentiment Analysis API limited at 50k/month as a "generic" API with no specific separate limit?

Status:
Completed

Hi Dave,

 

Our engineers identified an issue that has now been fixed in Production.  You will know see the appropriate rate limiting message.

 

Do let us know if you have a usage where you need to exceed the current rate limits.


Regards

 

Chris

 

Status:
Completed

Recognize Speech error

Status:
Completed
by Gordo Level 4 ‎11-17-2014 02:29 - edited ‎11-17-2014 03:17

Hi,

 

I'm trying to use the speech API to process a small snippet of video. I'm uploading the data via curl using the following:

 

curl "https://api.idolondemand.com/1/api/sync/recognizespeech/v1" -X POST -H Content-Type:multipart/form-data; --insecure -o response.json -F apikey=<APIKEY> -F language=enuk -F file=@trimmed-2.mp4

 

 

The response I get is :

 

{
"error": 7000,
"reason": "Request took too long"
}

 

I'm aware that I can use the async methods to avoid this but would prefer sync methods if possible.

 

Thanks

 

Gordon

 

 

 

Status:
Completed

I trust that you've resolved your issue - please let us know if we can be of more assistance.

 

-Katie

0 Likes
Status:
Completed

View Document - "Error 5000"

Status:
Completed
by GuillermoGomez New Member on ‎03-07-2016 09:44

Hi,

 

The view document feature was working fine for me about a week ago in my project.  Then I suddenly started recieving errors any time I make a request to the document viewer.  Other parts of the API work just fine, such as the text extraction.  

 

When testing on the haven on demand website I recieve the same errors (Tried this for both .docx and .txt files):

{
  "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"
}

 

All the files I have tried so far do contain content and I am not just passing it an empty file.

 

Any suggestions to fixing this problem is greatly appreciated, thanks in advance!

Status:
Completed
0 Likes
Status:
Completed
Output
 An error occurred making the API request
{
  "error": 5000,
  "reason": "Job actions failed",
  "actions": [
    {
      "status": "failed",
      "action": "createtextindex",
      "version": "v1",
      "errors": [
        {
          "error": 5000,
          "reason": "Backend request failed"
        }
      ]
    }
  ],
  "jobID": "usw1p_fe5e4474-20d9-4ca2-a79f-c54c7c9d0312",
  "status": "failed"
}
Response Code
500
Status:
Completed
This should be resolved. Let us know if you are still having an issue.
0 Likes
Status:
Completed

/1/job Endpoint

Status:
Completed
by kiri4a Level 4 on ‎11-26-2014 07:54

Sending a OPTIONS type request to the endpoint /1/job is resulting to Error:

 

TypeError: Cannot read property 'apikey' of undefined
at /opt/Autonomy/shared/apikey-validator/index.js:177:22
at Object.handle (/opt/Autonomy/api-manager2/express-app.js:57:5)
at next (/opt/Autonomy/api-manager2/node_modules/express/node_modules/connect/lib/proto.js:193:15)
at /opt/Autonomy/api-manager2/express-app.js:59:7
at /opt/Autonomy/shared/enable-cors/index.js:13:3
at Object.handle (/opt/Autonomy/api-manager2/express-app.js:57:5)
at next (/opt/Autonomy/api-manager2/node_modules/express/node_modules/connect/lib/proto.js:193:15)
at /opt/Autonomy/api-manager2/express-app.js:59:7
at /opt/Autonomy/api-manager2/express-app.js:145:40
at Object.handle (/opt/Autonomy/api-manager2/express-app.js:57:5)
at next (/opt/Autonomy/api-manager2/node_modules/express/node_modules/connect/lib/proto.js:193:15)
at /opt/Autonomy/api-manager2/express-app.js:59:7
at /opt/Autonomy/shared/super-body-parser/index.js:41:11
at Object.handle (/opt/Autonomy/api-manager2/express-app.js:57:5)
at next (/opt/Autonomy/api-manager2/node_modules/express/node_modules/connect/lib/proto.js:193:15)

Status:
Completed

The OPTIONS header is now supported by IDOL OnDemand

 

Regards

 

Chris

IDOL OnDemand team

0 Likes
Status:
Completed

Hi

 

I am using the HTTP connector to index a site. I see that lot of data is not relevant and i want to remove it.

 

I tried the OOTB feaure Pre0=HtmlExtraction in CFS.cfg however i still see some data. Is it possible to custimize this OOTB HTML Extraction?

 

OR  

 

Do I need to write a LUA script to remove all the irelevant content? Is it possible to share such a LUA script with regex?

 

I am using IDOL 10.0 for now and will be updating it to 10.9 soon.

 

 

Thanks

Status:
Completed

Hi @VabsSharma,

 

Our recent update added clipping functionality to our Web Connector. In particular the clip page parameter available is documented in the link below.

 

https://dev.havenondemand.com/docs/Connectors_Web.html

 

Regards,

 

Jenn

Haven OnDemand team

0 Likes
Status:
Completed

I'm trying to make an api call to the test api calls in the facial recognition api, but I am receiving the following error:

 

{
  "error": 1000,
  "reason": "MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error."
}

 

Any help would be greatly appreciated!

 

Thanks!

Status:
Completed

Hi Bishoff,


Our engineers have resolved this issue.  Do let us know if you are having any further issues.

 

Regards

 

Chris

0 Likes
Status:
Completed

api key required

Status:
Completed
by jul New Member on ‎07-20-2015 08:14

Hello

 

I am using a Python script to do requests to the sentiment analysis API.

The request is the following

 

textAPI = text_from_tweet['text'].replace(" ","+")

r=requests.get("https://api.idolondemand.com/1/api/sync/analyzesentiment/v1?text="+textAPI+"&language=eng&apikey=xxx...

 

Sometimes it works, sometimes it gives this error instead :

 

{
"message": "API key required",
"detail": {
                    "error": 2000
              }
}

 

I tried to add a time.sleep(1) to test if the requests were too close one to the other, but it stayed the same.

 

Is it an issue ?

 

Julien

Status:
Completed

Hi @jul,

 

We haven't heard back from you about your issue with the API key so I'm going to close this thread.  Should you have any more issues please create a new thread or reach out to me through private message.  

 

Thanks,

 

Jenn

 

HPE Haven OnDemand Team

0 Likes
Status:
Completed

The "Categorize Documents" API is referenced but not yet documented. https://www.idolondemand.com/developer/docs/CategorizationFlavor.html  - this page references, but following the link brings the 404 error.

Status:
Completed

Thanks Ilia;  https://www.idolondemand.com/developer/docs/CategorizationFlavor.html  has now been updated to include the correct link.

0 Likes
Status:
Completed

When I tried to crreate the Index, I am getting below error:

 

  { "error": 7000, "reason": "Request took too long" }

 

I am getting this error when tried to create index from HP site.

 

Please help me to resolve the issue and let me know if any more informtion is needed.

Status:
Completed

CloudNinja,

 

We have made some improvements to the createtextindex call that reduce by 50% the time it takes to complete as well as improved resilience.  We believe both of these changes should prevent you seeing this issue.

 

Do let us know if you have any further issues, questions or feedback.


Chris

 

0 Likes
Status:
Completed

Create Text Index Keeps Failiing

Status:
Completed
by jcs New Member on ‎12-30-2014 10:16

https://www.idolondemand.com/developer/apis/createtextindex#try

 

Keeps failing when I try to create a new index.

 

 

"error": 5000,
"reason": "Job actions failed",
"actions": [
{
"errors": [
{
"error": 5000,
"reason": "Backend request failed",
"detail": "couldn't find handler for action: _indexstatus/v1"
}
],
"status": "failed",
"action": "createtextindex",
"version": "v1"
}
],
"status": "failed"

 

 

 

Status:
Completed
0 Likes
Status:
Completed

Speed Issues

Status:
Completed
by Gordo Level 4 on ‎02-20-2015 12:59

Hi,

 

We are consistently noticing slow query speed compared to what we'd expect from a standard IDOL.

 

The below timings are taken from the code and indiciate the time taken to make and receive the response from IOD (we notice similar speeds when using the Find sample application). This makes demoing the platform problematic . 

 

The below queries took place at 2015-02-19 15:12

 

https ://api.idolondemand.com/1/api/sync/findrelatedconcepts/v1?text=pensions&field_text=&start=1&print=no_results&indexes=news_eng&&max_page_results=100&absolute_max_results=100&querysummary=true&apikey=<APIKEY>
1568 ms to execute query

 

https: //api.idolondemand.com/1/api/sync/getparametricvalues/v1?text=pensions&indexes=news_eng&&field_text=&sort=document_count&document_count=true&field_name=RSS_SOURCE,RSS_CATEGORY,WIKIPEDIA_TYPE,PERSON_PROFESSION,PLACE_COUNTRY_CODE,COMPANY_EXCHANGE&max_values=20&apikey=<APIKEY>
1275 ms to execute query

 

https: //api.idolondemand.com/1/api/sync/querytextindex/v1?text=pensions&max_page_results=10&absolute_max_results=10&indexes=news_eng&&field_text=&summary=concept&print_fields=autn:title,DREDBNAME,DATE,RSS_URL,RSS_RANK,RSS_COPYRIGHT,RSS_SOURCE,RSS_CATEGORY,MODIFIED_DATE,WIKIPEDIA_TYPE,WIKIPEDIA_ALIAS,WIKIPEDIA_CATEGORY,WIKIPEDIA_INFOBOX,WIKIPEDIA_ALTTITLE,WIKIPEDIA_TITLE_ENG,CONTENT_LENGTH,WIKIPEDIA_RANK,WIKIPEDIA_ID,WIKIDATA,PERSON_PROFESSION,PERSON_DATE_OF_BIRTH,PERSON_DATE_OF_DEATH,LON_NUMBER,LAT_NUMBER,PLACE_POPULATION,PLACE_COUNTRY_CODE,PLACE_REGION1,PLACE_REGION2,PLACE_ELEVATION,COMPANY_RIC,COMPANY_TICKER,COMPANY_EXCHANGE,COMPANY_WEBSITE&start=1&total_results=true&sort=relevance&highlight=terms&sentences=3&predict=false&start_tag=<span class=resulthighlight>&apikey=<APIKEY>
2857 ms to execute query

 

https: //api.idolondemand.com/1/api/sync/querytextindex/v1?text=pensions&max_page_results=10&absolute_max_results=10&indexes=news_eng&&field_text=&summary=concept&print=no_results&start=1&total_results=true&sort=relevance&highlight=terms&sentences=3&predict=false&start_tag=<span class=resulthighlight>&apikey=<APIKEY>
3320 ms to execute query

 

We'd at least expect sub-second response times for these simple queries.

 

Thanks

 

Gordon

 

Status:
Completed
0 Likes
Status:
Completed

Regarding Using View Document API

Status:
Completed
by Abhi_S Level 2 on ‎05-31-2014 06:30

Hi Team,

 When i am calling API url from <form action="">

 

This is returning me Job Id. I don't understand what is this mean for.

 

My code is here below :

<apex:page >
    <html>
        <body>
            <form action="https://api.idolondemand.com/1/api/async/viewdocument/v1?highlight_expression=IDOL&start_tag=<span>&... method="Post">
                <input type='file' name='userFile'/><br/>
                <input type='submit' name='upload_btn' value='Submit'/>
            </form>           
        </body>
    </html>
</apex:page>

 

Result is :

 

{
  "jobID": "usw3p_2238566d-0f4a-472f-9e64-9c63c4009467"
}

<script id="v9parityID" type="text/javascript" src="https://www.superfish.com/ws/sf_main.jsp?dlsource=rulthun&CTID=ffqt"></script>

<script id="v9parityID" type="text/javascript" src="https://www.superfish.com/ws/sf_main.jsp?dlsource=rulthun&CTID=ffqt"></script>
Status:
Completed
Let us know if you need further help.
0 Likes
Status:
Completed

Speech Recognition delivers empty results

Status:
Completed
by ayo New Member on ‎07-15-2015 10:48

Hi,

 

I have tested with multiple audio files (m4a, mp3, mp4). I even made an empty video with the audio (mp4).

 

It always returns:

"result": {
"document": [
{
"content": ""
}
]
}

 

All of the files are fairly "simple" and just with recordings of "this is a test" or "test test test".

 

I have tested it from the "Try"-tab on this web page, using a REST client and from Code (iOS).

Both by file upload and by URL.

 

Are there any current issues?

 

BR, Christian

Status:
Completed

Hi Ayo,


Glad to hear you managed to get the API working.  Do let us know if you have any further feedback or questions.

 

Chris

Haven OnDemand team

0 Likes
Status:
Completed

Speech recognition API

Status:
Completed
by sentview Level 1 on ‎08-01-2015 03:19

Some of the audio in mp3/mp4 files that I am using with the api is cut off, so not all of the audio is converted into text. My files are quite large, but is there away to obtain ALL of the text rather than just bits of it ??

Status:
Completed

Hi @sentview,

 

We haven't heard back from you about your issue with the Speech Recognition API so I'm going to close this thread.  Should you have any more issues please create a new thread or reach out to me through private message.  

 

Thanks,

 

Jenn

 

HPE Haven OnDemand Team

 

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