Added rate limiting section to both API v1 and v2 docs pages
Thank you, yes, all methods of creating tasks are working now.
Would you be willing to consider setting the logout timer back to what it was previously? Or at least something midway between what it is now and what it was before? I’m logging in two or more times a day.
Not intentional! I’ll see what I can figure out.
It seemed like some users were still having trouble creating tasks. I’ve pushed something that will hopefully solve the problem.
However:
Looks like GCP is currently having an outage, so you may see issues with TaskRatchet for a while.
I’m unable to create new tasks, and the ones I did create today have disappeared. I made several no problem, but when I went to edit the time on one of the tasks, it said “internal server error” or something similar, all the tasks disappeared, and now I can’t create new ones at all.
Happy to do any and all troubleshooting with you! I just hope I don’t end up getting charged for all those tasks because they were due to be completed this afternoon.
@shandog Yikes, thanks for the heads up! I’ll see if I can figure out what’s going on today.
Could you pm me or email me at nathan@taskratchet.com to give me your taskratchet account email address?
Also, if anyone thinks that a bug has contributed to them failing to complete a task on time, definitely email support@taskratchet.com (or preferably reply to the charge email) for a cancellation / refund!
Deployed a fix that should fix @shandog’s issue. Seems that updating the due date on an existing task may have been breaking things.
The API now does a better job of returning informative 404 messages when a user ID is requested that doesn’t exist.
I’ve restarted my Beeminder goal for putting time into improving TaskRatchet.
We switched from Freshdesk to Zoho Desk for support. I’ve removed the old Freshdesk widget from the web app.
- Added
GET /api2/me/token
- Removed
api2_token
from/api2/me
response - Documented token routes in API v2 docs
- Expanded routes to include
/api2/
prefix in API v2 docs
@alys A bit ago I deployed a new auth system, hoping this fixes the issue you were seeing with getting logged out all the time. Can you confirm if this is working better now?
Fixed a bug where uncling prevented you from being able to see your tasks list.
Just set up a status page:
The TaskRatchet.com footer now links to the status page
Added a message to the TaskRatchet API v1 docs stating that API v1 will be sunsetted on September 12.
I’ve also sent emails to the users who’ve used v1 of the API in the last month.
Added the ability to query your tasks by status and due date, and documented how.
Just pushed a bug fix to prevent the web app from using stale auth tokens.
API v1 is now shut down.
curl 'https://api.taskratchet.com/api1/health'
{"error":"api_v1_gone","message":"API v1 has been shut down. Please migrate to API v2.","docs":"https://docs.taskratchet.com/api-v2.html"}