ilock VS flask-apscheduler

I had this exact issue, so I used Ilock combined with a cached var to ensure only one worker did the initial load.

I had to use it because I setup scheduled tasks in my init.py. Flask APScheduler

When I’ve previously made bots, I’ve typically used an external service such as Render’s cron job service or Google’s cloud scheduler to handle the timing of my bots. But for @noun__verb, I used flask-apscheduler to set up the timing. This might be better for smaller projects, but you may want to consider a cloud service as you scale.

Hopefully, this can be a starting point for you to get started with generating refresh tokens. As a next step, if you are using Flask you may want to consider using a schedular to update your refresh tokens regularly in an automated fashion. Additionally you may want to consider saving your tokens to a database in a secure fashion. This code sample can also be extended to allow you to connect to any of the endpoints that support v2 and can be deployed to a server as part of a more complete application.

Flask-APScheduler might be what you're looking for.

Any framework to add dynamically job scheduling like cron ? I find https://github.com/viniciuschiele/flask-apscheduler . Anything else like this?

Flask-APSScheduler would work well for this.

To extend this, there is flask wrapper for apscheduler. I worked with this, and it's OK IMO. https://github.com/viniciuschiele/flask-apscheduler