Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

existing appointment is flagged as available and keeps being "reset" to the same date/time stopping the scheduler #148

Open
abondarev84 opened this issue Jul 30, 2024 · 14 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@abondarev84
Copy link

the automatic search finds as first available the same date that I have already set and as a result it cancels existing, sets the same one and exits.
updated to the latest version today.

@abondarev84 abondarev84 changed the title existing appointment is flagged as available and keeps being "reset" to the same date/time stopping teh scheduler existing appointment is flagged as available and keeps being "reset" to the same date/time stopping the scheduler Jul 30, 2024
@itsmateen
Copy link

change cancelIfExist to true in config file

@abondarev84
Copy link
Author

it is set to true.
what happens is that it first cancels an appointment and then sets the exact same one which causes it to exit (as intended I'm guessing).

but the new and old appointments are exactly the same one (time/date/place).

@phamleduy04
Copy link
Owner

sorry for the delay, do you still have logs?

@phamleduy04 phamleduy04 added the need-infomation Further infomation is needed label Aug 6, 2024
@phamleduy04
Copy link
Owner

Because the way the bot is coded for now is:

  • If you have an appointment -> the bot will check for a new one -> if the new one is available (doesn't check for the same day/same time for an old appointment) -> bot will cancel and book the new one.

What I think is that 2 appointments have the same date/time that are causing issues.

@abondarev84
Copy link
Author

Since the appointment is in the past (I'm already done).
I don't know if I can test again however, what was happening is that the exact same time and date (and location of course) was being set time and time again (I had like 5 or more emails about CANCELED and then RESERVED, or whatever they send) and I didn't realize at first that it was the exact same one so I was just restarting the program to get a closer date.

I actually saved the log (just now realized)

[07/30/2024 11:50:27] WARNING -> Invalid date in config.yml, using current date
[07/30/2024 11:50:27] Texas Scheduler v3.1.1 is starting...
[07/30/2024 11:50:27] Requesting Available Location....
[07/30/2024 11:50:27] WARNING -> You have an existing booking at Austin South 08/06/2024 09:00 AM
[07/30/2024 11:50:27] WARNING -> The bot will continue to run, but will cancel existing booking if it found a new one
[07/30/2024 11:50:29] Found cached location selection, using cached location selection
[07/30/2024 11:50:29] If you want to change location selection, please delete cache folder!
[07/30/2024 11:50:29] Checking Available Location Dates....
--------------------------------------------------------------------------------
[07/30/2024 11:50:40] Pflugerville Mega Center is not Available in around 0-60 days from 07/30/2024!
[07/30/2024 11:50:45] Georgetown is not Available in around 0-60 days from 07/30/2024!
[07/30/2024 11:50:48] Taylor is not Available in around 0-60 days from 07/30/2024!
--------------------------------------------------------------------------------
[07/30/2024 11:50:51] Austin North is not Available in around 0-60 days from 07/30/2024!
[07/30/2024 11:50:58] Austin South is Available on 8/6/2024 9:00 AM
[07/30/2024 11:50:59] Slot hold successfully
[07/30/2024 11:50:59] Booking slot....
[07/30/2024 11:50:59] Canceling existing booking 172636096
[07/30/2024 11:51:00] Canceled booking successfully
[07/30/2024 11:51:02] Slot booked successfully. Confirmation Number: 133590796
[07/30/2024 11:51:02] Visiting this link to print your booking:
[07/30/2024 11:51:02] https://public.txdpsscheduler.com/?b=133590796

@abondarev84
Copy link
Author

my uneducated generic guess would be that there is somewhere a <= instead of < or something essentially similar to this.
OR that the function that compares dates and "distance" to today implicitly gets a comparison result as true when "distance" to the new appointment is the same as current one.

@phamleduy04
Copy link
Owner

The bot doesn't do any comparison, will need to add this part to the code. I will fix it on the new release after #156. Thanks :)

@phamleduy04 phamleduy04 added bug Something isn't working enhancement New feature or request and removed need-infomation Further infomation is needed labels Aug 6, 2024
@abondarev84
Copy link
Author

for future users :-)

Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Dec 20, 2024
@abondarev84
Copy link
Author

is this still relevant?
does it still function? (there was a note about txdps changing their api or something like that)

@github-actions github-actions bot removed the Stale label Dec 24, 2024
@phamleduy04
Copy link
Owner

I havnt work on this yet. Just make the bot working again

Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Jan 24, 2025
@phamleduy04 phamleduy04 removed the Stale label Jan 24, 2025
@phamleduy04 phamleduy04 self-assigned this Jan 24, 2025
Copy link

Hi there 👋

You are using the free plan of the Create Issue Branch App.
Due to its popularity, offering the App for free is becoming too costly for me.
The free plan is therefore going to be deprecated on March 1st, 2025.

If you want to continue using this App, please upgrade to the Developer plan.
The Developer plan costs only $1 per month (or $10 yearly).
You can upgrade on the GitHub Marketplace

If you have any questions reach out to me by opening an issue.
To disable this message, insert freePlanWarning: false in your configuration YAML.

@phamleduy04 phamleduy04 pinned this issue Jan 24, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants