Hi all, im building a small tool that should send out a notification to a person once a flight that i am on board has departed.
I have succesfully built a Google Sheets template with upcoming flights → the todays flight is being sent to flightaware and data is pulled via api.
If the flight has departed its sending a notifcation. Scenario end.
Where i am stuck now is the fact that i need to make the scenario sleep for 30 min and rerun the api request later, if the flight has yet not departed.
So i want a module that check departure, if not departed, wait 30 min and if necessary, run the requested and the wait time again.
I have sucessfully managed that with a sleep module 300sec *6 sleep repeats, but i then get very quickly to the 40 min scenario limit.
I arrive at a airport lets say 1h 30 min before departure (thats actually the trigger in the end, entering a geofence), so with an avg departure delay i need at least a total of a 2h break module split in 30 min sections.
I saw that video here with the work-around but i always get a error:
The error i get: The operation was completed with a warning. Failed to map ‘value’: Function ‘if’ finished with error! Function ‘formatNumber’ finished with error! ‘NaN’ is not a valid number or using unsuitable separator.
I have too mention alongside that i am on the free plan.
Looking forward to your ideas, suggestions and improvements.
Hello @danielk, I can think of so many improper ways to use your scenario. Like, thanks for the money, you’ll never catch me…
Anyways, instead of sleeping, consider integrating Make break error handler as a way to delay things by up to 12 hours.
I admit, you have the new challenge of forcing a error, and then picking up after it.
Alternatively, why not push the delay to a data storage, and then using a second scenario that monitors that data storage, then runs the first script again.
What you want is possible, just your scenario structuring will have to change to accomodate more than one scenario at play or using incomplete executions.
Hi @ImMichaelCannon , i’m getting devasted by trying this now since 3 days in a row and i cant make it work. Tried with ChatGPT etc but it wont work ffs. May i ask you if its fine to share the blueprint with you and you quickyl implement one of the Break error handlers? I really dont know further as my nerves and ops (already purches the bigger pack) are coming to an end…
Thanks @ImMichaelCannon, highly appreciated!!!
Maybe just 1-2 quick thoughts on the topic. I need to run this basically from entering the airport until final departure, so lets say every 30 min. Will this work out if we have to keep in mind the 40-minute execution timeout limitation?
Blueprint 5 is the scenario which is posted above. blueprint (5).json (52.0 KB)
I have created another scenario in the hope that i can make it run, where its maybe easier to fix it - the watch emails module.
I have a Flightradar24 Silver membership where i can receive emails when a flight that i entered has departed - but the scenario will run everyday.
Therefore, my scenario watches my inbox and parses the text only on the day of the flight and puts it in a notification.
Problem is here the scheduling. I need it only on the day of a departuring flight (which is noted in my Google Sheet). It runs once when i enter the airport, but the email comes only at departure. I need something like if entered place X at defined date in Google sheets, then check all 30 min my mail. If found, send notification and scenario is done. The blueprint is the v6 blueprint (6).json (41.7 KB)
What is easier to fix? Im fine with any of the scenarios
Thanks for the help, its highly appreciated!
Hiya @danielk; the easy answer first. Using the Break error handler seems to reset the scenario time limit. And notice that the break time before attempting again is more than 12 hours.
Next, for only running when you’re flying and staying relevant to the time zone you’re flying from is entry to a bigger system of the non-inclusive following.
Flight logger - I use Tripit so there’s reminders about flights ahead of time so a mail monitor could create a flight schedule that is checked for a later module, like the in the air notifier
Timezone awareness - Might be a function than a scenario
Flight delay handler - Could just be a push to the flight logger from the in the air notifier
In the air notifier - checks for logged flight, yes checks that the plane left, yes send notice, no add to flight logger
Looking through your notes again, it could be that the in the air notifier is a common scenario called from another scenario or two that track pending flights.
Hi @ImMichaelCannon thanks for your message! I made it work with a small workaround with my flightradar subsricption and their alerts. for now not the perfect option as i need to enter the flights there ahead, but then - it works.
May i ask you if its fine to share the blueprint with you and you quickyl implement one of the Break error handlers? I really dont know further as my nerves and ops (already purches the bigger pack) are coming to an end…
