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

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

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

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

timeouts

Status:
Completed
by sinpa New Member ‎12-30-2014 01:39 - edited ‎12-30-2014 01:43
Hi I'm getting timeouts. Sample response using my Account: "We were unable to perform this search, please try another search." For this req: https://api.idolondemand.com/1/api/sync/querytextindex/v1?text=electric&indexes=my_index&print=all&a... ... In postman I get: { "error": 7000, "reason": "Request took too long" } Please help with this, I'm trying to develop a demo for customer Thanks!
Status:
Completed

Let me know if anything changes!

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

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

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

 

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

Create Index Problem

Status:
Completed
by Gordo Level 4 on ‎05-06-2015 01:46

I'm trying to create two new custom-field indexes on IoD.

 

Apparently I have 0/50 units used (though I have 1 index with custom fields)

A new custom index costs 12 units

When I try and add a new index the message says 

 

"Unable to create text index: Reached index quota - need 12 units, have 8 units left"

 

Can you explain why this is?

 

Thanks

 

Gordon

 

Status:
Completed

Hi Gordo,

 

The incorrect display of text index quotas you identified as been removed.

 

You can view you quotas at any time via: https://www.havenondemand.com/account/quotas.html

 

Regards


Chris

Haven OnDemand team

 

 

0 Likes
Status:
Completed

The https://www.idolondemand.com/developer/docs/CategorizationFlavor.html page is supposed to describe the CategorizationFlavor and its limits just like the other flavors pages do. But in fact it currently describes limits of another flavor named StandardFlavor. Please update the CategorizationFlavor description page with correct relevant limits.

Status:
Completed

The text has been updated.  Thanks again for taking the time to report this issue.

 

Chris

IDOL OnDemand team

0 Likes
Status:
In Progress

Patents Date Restriction

Status:
In Progress
by Gordo Level 4 on ‎03-24-2015 05:12

Hi, I'm trying to do some date restrictions on the patents corpus:

 

curl "https://api.idolondemand.com/1/api/sync/querytextindex/v1?text=DREALL&field_text=RANGE%7B1364125215e%2C.%7D%3Apatent_pub_date+AND+RANGE%7B.%2C1427197215e%7D%3Apatent_pub_date&indexes=patents&apikey=<APIKEY>"

 

This returns an error  

 

{
  "error": 4024,
  "reason": "Job actions failed",
  "actions": [
    {
      "errors": [
        {
          "error": 4024,
          "reason": "Field_text contains operations on unoptimized fields",
          "detail": "'The fieldtext contained an operation against a non-optimized field.'"
        }
      ],
      "status": "failed",
      "action": "querytextindex",
      "version": "v1"
    }
  ],
  "status": "failed"
}

 

Is the patent index not setup to handle this?

 

Thanks

 

Gordon

 

Status:
In Progress

Gordo,


Thanks for taking the time to raise this issue.

 

The Patent index is not currently configured for data operations, however this is intended.  Our engineers will be making the appropriate changes and we will let you know when this is complete.

 

Regards

 

Chris

IDOL OnDemand team

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

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 server caching results

Status:
Completed
by djpidol Level 3 on ‎05-14-2015 07:44

Speech server appears to be delivering the same result for different target URLs, I have checked the request log to verify that my code is sending different URL mp3

source code https://github.com/djpidol/bearded-octo-sansa/blob/master/thought_for_the_day.rb

Status:
Completed

A number of updates to the Speech Recognition API have been deployed recently and this issue should now be resolved.


Regards


Chris
Haven OnDemand team

0 Likes
Status:
Open

Hello,

 

While calling https://api.havenondemand.com/1/api/sync/analyzesentiment/v2?text=hello&apikey=<withheld>, I'm getting:

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

 

It was working well around 8 hours ago. Any issues with the handling today?

 

Thanks in advance!

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