[#464] Internal error from getStartTimeMatrix

Bug Reports
,
1

Migrated from Redmine #464 | Author: Daniel Horowitz
Status: Feedback | Priority: Immediate, there is BUG! | Created: 2020-01-22

We are getting an error from the getStartTimeMatrix transaction: {
code: -32603, message: ‘Internal error’, data: }

Sending this as input: [“2020-01-19”,“2020-04-18”,1,97,null]

We are unable to process bookings until this is resolved

2

Juan Villegas wrote:

Hi, I’m a Software Engineer working on Smylen with Daniel Horowitz, who opened this topic above.
We have been using the getStartTimeMatrix function to look 3 months in advance (as per our application’s requirements), but now after some research it seems the API fails with a cryptic “Internal Error” if the difference between the “from” and “to” arguments is X > 31 days.
Is this change something you guys are aware of, and if so, working on it? Or is it intended behavior?

Thanks
Juan

3

Dmytro Bondarev wrote:

Hi! It is intended behavior, please call with period less than 1 month.

4

Juan Villegas wrote:

Thanks. Wondering if there is a Changelog or something where we can track the progress of the API?
I don’t want to be rude here, but the API is something your company is not giving away for free, but rather it’s part of the paid subscription. As such, I’d expect at least to be notified in advance of breaking changes like this, and at a bare minimum, to have these changes documented somewhere. If you visit the API’s doc page, the method doesn’t say anything about the restrictions on the parameters. How can the consumers of the API know that it only tolerates a period of 1 month if the error we get back is a (negative) integer and an Internal Server Error as message?
Thanks
Juan

5

Redmine Admin wrote:

Hi, we understand this can cause inconvenience for developers and are sorry about it. Unfortunately we noticed some users start to produce extremely heavy load on server by making many API requests with long periods in parallel mode. This results in kind of DDoS attack on our servers and we had to act quickly to keep systems operational.
We are sorry again to introduce certain restrictions and hope for you understanding.