Something is wrong with «other date» function in «add additional play» (it started after the 26/12-2024 update). Whatever date and time I put in, it Trakts it like it was just now. For instance: The time is 9:27 and I know my episode is done at 9:55. So I manually write 9:55 and hit «enter», and then it says I finished the episode at 9:27.
Which device? Or web?
I’m having no issues here with an episode I tracked about 9 hours ago with the other date method on iOS beta.
Yeah, I should have mentioned that. The error occurs on the webpage using Chrome and Safari (on a Macbook Air). It occurs on iPhone using Safari. I don’t know about the app (don’t have it).
Edit: Just tried it on a Mac Mini 2023, Google Chrome. The error still occurs.
Edit: Turns out I can Trakt back in time, but not ahead in time.
There were several issues with people or data imports adding dates far in the future, so I updated the behavior to not allow that.
I’m curious why you don’t use the watching now (check in) button? That will start watching now and commit to your watched history with the runtime added (in the future).
I Trakt that way because it’s the most reliable. I’m very OCD when it comes to Trakt, and the Plex Scrobbler is off by 3-15 minutes, and the check-in don’t care about bathroom breaks and that I sometimes skip the end credits.
I would love if you will allow Trakting in «the future» again – perhaps have a time limit at four-five hours (from any given point)?
2 Likes
Then why add it in the future and not just watched? Why add watches ahead of time?
I have no issue with adding something manually that I watched 10 mins ago or just watched.
I don’t understand the use case of now adding something you will complete in 10 minutes.
I never use the watching now function either.
Why I use Trakt the way I do is irrelevant. I just thought it was a bug, seeing I’ve been doing it that way for close to 8 years and suddenly it didn’t work.
Hi @Ohifriend, @justin, did something change in the code for Trakt where users are able to mark episodes and movies as watched in a future date and time?
I just tried now and realized even though i picked a future date/time, it only marks as currently date/time as watched, so it no longer works.
I used to be able to. I know it’s a bit odd, but sometimes, I already know when I will be done with an episode or movie and want to mark it as watched when I will finish watching it, but not able to anymore.
For example, I have a movie item which i wanted to mark as watched for today (Saturday 12/28) at 8pm ET while it’s only 3:06pm ET right now. It should have marked it as watched at 12/28, 8pm ET, but instead it still marked it at 3:06pm ET. This is happening from the website as well as the iOS app. I assume something has changed in the API.
Are you able to confirm and able to let us know why this change was made? Unless it was a bug, and if so, when it can be fixed.
1 Like
looks like i found my answer…
I guess marking as watched in a future date/time is no longer allowed… that’s a shame… i usually do this for a few things for in terms of accuracy for when i plan to have finished watching it bc i’m watching it live. i would mark it in the future so that it’s accurrate to when i actually finish watching something rather than marking it as now which i’m still watching. I could mark it as watched when i finish watching it but it was just a precaution in case i forget to mark it as watched. I could use check-in, but sometimes i already and in the middle and if i click check-in, it would not be accurate.
1 Like
The only thing I’m worried about is the service changing dates before release now… I’ve already had to redo half my watched library because duplicates got deleted against my will and fear this future date thing is 1 step away from deleting some things I put in the early 1900s because I couldn’t remember when I actually watched the content.
I’m not sure why features get taken from some users instead of solving the actual problem in the backend.
It shouldn’t be that difficult to make such changes an checkmark to enable or disable on a per profile basis.
Seems to be a common trope of “I don’t use it like this, so you shouldn’t either”.
1 Like
I will review these comments next week and might allow some amount of time in the future as valid since the use cases mentioned make sense.
In general, marking stuff in the future is just not a typical use case and the change was made to fix issues with the Trakt importer and media centers sending dates in the future that could never be accurate.
There’s no need to change anything with dates in the past, because that is a valid use case to build up what you’ve already watched. My change was only related ro watched dates in the future.
2 Likes
Thank you. I hope you will reconsider and allow us to Trakt a little bit into the future. Personally, I only need a couple of hours leeway.
I’d just like to leave a little more info: Since the change I now have to Trakt manually after the episode/movie is done, and then remove the Plex-scrobbler-Trakt (because it’s off by several minutes, and me and my OCD need it to be accurate).
Before the change, the manual ahead-in-time Trakt would override the scrobbler.
It would save me and my anxious head a lot of frustration if some leeway was allowed.
Came here looking to see if anyone else was having this issue. It seems so. I also would like to be able to mark stuff watched in the future. 24h at the least. Sometimes I’ll mark stuff as already watched in the morning, when I know I’ll be watching a show live that evening. And I already know at what time it ends.
Or just now, when I started watching a movie that lasts 2 hours and I want to mark it done in 2 hours. It doesn’t let me do that. Instead it marks it at the current time. If I put on a movie at 8 and it takes 2 hours, I wanna mark it at 10. Not at 9:14. This was never an issue. But somehow since the last update, it has become so.
Please consider rolling back this behavior. Thank you.
2 Likes
You can add up to 24 hours in the future now. The Trakt importer won’t allow future dates, but the website, API, and apps will allow a small grace period.
4 Likes
Thank you! That’s perfect! I never need to add anything over 24 hours in the future. Usually do it for same day but later in the day when I do.
Thank you, Justin! This is wonderful.
There is definitely a bug with “other date”. I enter past years via the calendar, but it records as today. Tried in web Chrome/Firefox (Windows). If you look at devtools, the date sent to the server is correct (the one I select in the calendar). But seems the server just discards the date, and saves today’s date
The payload looks like this watched_at=2022+12+January+11%3A27&collected_at=2022+12+January+11%3A27. Possibly parsing issue, and the database just saves default value (now)
I can confirm this bug is happening from the website. When using that function from the ios and android app, it works fine. @justin
Current date/time: 1/17/2025 8:50pm ET
WEBSITE [FAILS]: Marked as watched using “Other Date” as 1/17/2020 8:50pm ET but it gets marked with 1/17/2025 8:50pm ET
IOS APP [PASSES]: Marked as watched using “Other Date” from as 1/17/2020 12:00am ET but it gets marked with 1/17/2020 12:00am ET
ANDROID APP [PASSES]: Marked as watched using “Other Date” from as 1/17/2020 12:00am ET but it gets marked with 1/17/2020 12:00am ET