gsomoza
commented
4 years ago Thanks for reporting this! The challenge we already know about is that the Harvest API often responds with "everything is OK" (200 status code + no error details in response body) when actually something is NOT OK. It's hard to predict when this will happen and it's hard to know exactly what to expect from the response body in order to "catch" it (since we know the HTTP status code they return is incorrect).
Unfortunately there might be no viable solution to this until Harvest fixes their API to return proper status codes...
Hi guys, my company is using your plugin and I've been noticing lately a significant percent of the time (maybe 0.5 or 1%) the time entry gets logged to the jira ticket but never shows up in harvest.
There's not any errors when this happens, jira reports that the time entry was added to harvest but when I view harvest it is nowhere to be found.
Today, dec 28, it happened twice (it's never happened twice on the same day before). Is there an API server down or something? If the harvest API server is down is the error reporting working so that your plugin doesn't think it successfully created a time entry in harvest? It seems to show a success message even when the harvest API call fails. That's just a theory, unfortunately.