-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to adjust run schedule? #9
Comments
So regarding the cookie portion. from the instructions on Claabs upstream, it seems that logins may only be valid for 8 hours. Regarding the job running ever four hours, It's possible it is attempting to login during that time and hangs, although I'd need logs with time stamps to validate that. |
Hi - can you pull in the most recent changes from main branch and see if this resolves your outstanding issues? |
I've updated and it's still not sticking to the schedule that I've set. There was one run around 10 hours, then another 40 minutes ago and another 3 minutes ago. The weird thing is that when I clicked on the solve captcha link, it tells me there's no captcha ID to solve. But then I tried the same link again just now and it works: Not too sure what's going on. Anyway, the schedule is still not correct... UPDATE: OK, something is definitely broken. The capcha emails have solved successfully after I visited the link, but I keep getting constant emails for the capcha and the cron schedule is set to 168 hours, which is every 7 days. |
Can you let me know if you are using the token method or the email/password/TOTP string? I have a feeling what is happening is the app is continuing in a loop. Because of the method we have to use with web worker for Heroku, it will attempt to restart 3 times from crashed until it will eventually sleep. What might be happening is the CAPTCHA workflow continually triggers a crash state, then restarts and continues again without sleeping the instance. Can you please try the email/password/TOTP workflow only? |
I modified the Github Workflow for "EpicGamesFreeGamesRun" to run the cron job every 7 days, i.e 168 hours. I ran the workflow and thought it would make a change, but I am still getting the "Epic Games Free Captcha" emails from Heroku every 4 hours or so.
It seem that I have to constantly generate a new cookie and update Github Secrets. I think if the run time is once every 7 days, it won't expire the cookie that quickly, but I can't seem to figure out why Heroku is still running the job every 4 hours.
The text was updated successfully, but these errors were encountered: