GroveStreams

ERROR: Could not locate matching endDate468

macedo123 private msg quote post Address this user
Why do I keep getting this message when trying to PUT data into a newly created Component ?

Only the sample Component Template from the Organization Bluepint work and allow for registration of new devices, any other manually create component fail with the following message :

SEND:

PUT /api/feed?compId=357926&amp;api_key=<my api_key>&amp;s1=29&amp;s2=12 HTTP/1.1

Host: grovestreams.com
Cache-Control: no-cache
Postman-Token: 5951edce-5976-22f0-4458-cd79771a3d69
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary7MA4YWxkTrZu0gW

RESPONSE

{
"message": "Could not locate matching endDate for interval during rollup while rolling up from Days to Months for Stream with id '<my api_key>'",
"errCode": "REQUEST_VALIDATION_FAILURE",
"success": false
}

Same error for manually create Templates either

Thanks, Luis
Post 1 • IP   flag post
MikeMills private msg quote post Address this user
We've had some issues with certain timezones. A component, and a template, has a timezone associated with it. If a feed doesn't include a template ID, then the organization Owner's timezone is assigned to the component (click your name then choose profile to see your timezone).

Determine what timezone is having the issue and let us know. You can try changing timezones too.
Post 2 • IP   flag post
macedo123 private msg quote post Address this user
OK, changed both timezones to "America/Sao_Paulo", witch is my current time, still got the same error, changed both to "Etc/GMT+0", got it to work, changed all back to "America/Sao_Paulo" and presto, everything is working fine, thanks!!
Post 3 • IP   flag post
macedo123 private msg quote post Address this user
Ooooops, created e new Component from the "fixed" template, getting the same error again:

{
"message": "Could not locate matching endDate for interval during rollup while rolling up from Days to Months for Stream with id 'XXXXXXXXXXXXXXXXXXXX'",
"errCode": "REQUEST_VALIDATION_FAILURE",
"success": false
}

Back to the drwaing board...
Post 4 • IP   flag post
MikeMills private msg quote post Address this user
It's some South American timezones we're experiencing issues with. I'm assuming you set the template timezone to Sao_Paulo when you got the last error?
Post 5 • IP   flag post
macedo123 private msg quote post Address this user
Yes, "America/Sao_Paulo", back on GMT+0, and no problems anymore, will keep it that way...already setup my devices to this time too...
Post 6 • IP   flag post
2581 6 6
Log in or sign up to compose a reply.
destitute