I'm looking for a way to be able to set my app to launch and carry out certain functions depending on the time and day of week. The app needs to be able to set the time and days of week, then run a specific function depending on that time and date. For instance if I set the app to run 1 function 12:00pm every Saturday, and another 3:00pm every Sunday, they can be processed in the background somehow. Essentially I want it to run like a scheduled background, where I might run an incremental backup during the week and a full backup on the weekend.
I've searched all over and can't seem to find any leads.
Any help would be greatly appreciated!
Thanks.
Take a look at Local Notifications: http://developer.apple.com/library/ios/#documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Introduction/Introduction.html#//apple_ref/doc/uid/TP40008194
Related
I have a Scheduler Job within Cloud Scheduler running to call a Cloud Function. Working as expected however I need to create multiple cron schedules for the same job, is this possible without recreating from scratch each one? There doesn't seem to be a Copy function.
Use Case:
Schedule 1 - Every 15 minutes Monday - Thursday
Schedule 2 - Every 15 minutes Friday SoD till Friday 22:00PM
Schedule 3 - Every 15 minutes Sunday 22:00PM till Sunday EoD
How can I achieve this, or do I just need to recreate all the schedules from scratch?
Posting this as a Community Wiki as it's based on #GuillaumeBlaquiere and #Al-dann comments.
At this point you going to need to recreate all of those schedules from scratch, however, you can automate the creation of new Jobs with a script, either with gcloud or terraform. This will make duplication, creation and deletion of Jobs easier and quicker as well as allow you to version it.
I've been getting this message returned in the JSON since last week when trying to get Google Classroom app usage reports via the admin api. Has anybody come across this issue before or know if it is some temporary issue with the service?
If I change the date parameters to 2020-10-12 it works and I have been able to obtain 'daily' data in this way for the last few weeks. (It seems that there is generally a delay of about 2 and half days before the reports become available for a given day, so this current delay seems to be much longer than usual).
I am using the classroom:timestamp_last_interaction parameter.
As of 2020-10-20, I can now access Classroom usage data for 2020-10-13. Maybe the lead time has increased to a week, which would be a shame, but easier to remember I suppose!
Will update if I uncover more.
If I have hundreds of triggers set to work on a specific day of the week within the same hour time frame (lets say Monday between 8 am to 9 am) - will they be executed in the way that will burden the least on the server?
If not - according to which consideration the execution time will be determine?
Is there a limtation of amount of triggers in an hour/day? What is it? (in Quotas for Google Services I found only a Triggers total runtime).
Thanks!
So here is a thing, I have some lawyer app, and he needs to set reminder for some case, that reminder could be tomorrow, next week, next month idk. I was thinking about using node-cron, thing is i dont know what will happen when my app restarts, I assume it will crash all my reminders, and the second thing is how much will I load my server if i got to much reminders, OR do u have some other advice for this solution, maybe something with setInterval and run it every hour or something like that?
node-cron is used to run code as you would with normal cron, but in JS :)
So even if your code is crushed and restarted it will look at time set by you to execute some code and will not crush reminders.
For example if you run some code with cron condition 0 0 1 * *, which means every month on 1st date at 00:00.
That means that even if your app is crushed at 15th of month and restarted at 20th of month, it will run your job at 1st of next month at 00:00.
Between for automatically restarting your app you can use forever or pm2 packages from NPM
Now about this question.
how much will I load my server if i got to much reminders
I don't think it will load your server. node-cron internally uses setInterval, which is not CPU consuming, so go and run your crons without fear.
I have a problem related to automatic task scheduling.
Currently i am able to find out when my customer has last credited his account, how am i able to find out whether he will pay anything in the next 3 days?
So if no payment has been made in the next three days for any customer, to automatically alert me preferably by a notification directly to my ipad.
I dont want myself to open the app for checks to be done only when i log in, because then if i jump on my application 6 days later, i could have had a customer that hasnt paid in 6 days when the app should have alerted me on the 3rd day so i could ring my customer up to deal with the matter.
I need to work in this matter due to the structure of my application and business.
I am able to monitor everything else but need some insight on how I can go about doing this. the current notification system inside the phone only fires based on time, and I cannot do interval checks where maybe i could run a background task, if that would work then i would have done it like that but thats not the case.
Pavan
If I understand your question correctly, you should compute the interval of the event that you want and post a wake-up timer that is that period of time from "now." If you need it through the notification center, then just handle it silently and clear it from the notifications.
Based on the discussion below:
You will need a little bit of server work. APNS looks complicated, but it really has very few moving parts -- especially if it is a private App. What system component is keeping an eye on Amazon? Do you have an App or web server? For example, if I were to poke a record into your system (purchased services) what workflow is triggered to notify Accounting to process an invoice and collections at a later date? Am I making any sense of your system architecture?
Perfect - you are done. You have all the system components you need and the rest is coding. The server app processes the accounts DB and finds new entries. If found, it publishes a record ID to the APNS server (Apple owns this server). You write code to register to receive the push-notification (subscriber). When you get a push, that will wake up your registered app with the record ID (and some other subscription stuff for bookkeeping -- but you are the only subscriber and only subscribing to one DB table -- so you can largely ignore. Now turn around and query based on that record. Done!