What happens to our scheduled process when an tom goes offline and when its restores? It may be cloud or local atom.
Thanks for all your helpful responses. Here is the correct answer, I am considering James Ahlborn and Darwin Collins answer as correct.
So, Collating all those responses, we get the right answer:
Please feel free to correct... My understanding, lets say you have a Local Atom. It has a process that connects to a local database. You have scheduled it to run at 3pm everyday.
At 2pm, your company looses internet link/access so your atom can not contact the platform. On your cellphone browser, you can see that the platform reports that your atom is offline.
At 3pm, your atom runs your scheduled process. If the process does not encounter a problem, then it will complete successfully. On your cellphone, the platform only says the atom is offline.
At 4pm, your internet access is regained. Your atom uploads the process results to the platform, and so you can now see the results as you normally do on the platform.
However, lets say your internal switch is down. (Atom has NO connection to database or internet) Your atom would attempt to run the process but it would generate an error, because it could not connect to your database. After you fix your switch, the atom can connect to the platform and upload the results. You would see the errors and would need to manually rerun this process.
ok... everyone, how is that? You think it works like that?
My response and additional questions:
Thanks for the response,Darwin. So, you mean to say that my processes metadata will be reported/uploaded to the atom(once again my atom comes online) even my atom is offline but my scheduled processes ran without having any issue because of my atoms offline status?
James answer confirming the above points as correct:
This is correct.
Happy Exploring Boomi.
You need to execute the processes manually when that happens.
It would probably be possible to create a process that could execute all the missed processes. I have thought about making one from time to time...
Thanks Leif for the response. That was helpful.
One more thing: When it comes online, does it execute the missed schedules Or does it execute the immediate next schedule?
Sorry to keep you waiting.
Yes, the schedules are activated again and will execute the processes set from after the Atom is online again, the immediate next schedule.
Example: your Atom goes offline at 4 am monday, gets online again at 6 am monday.
A process is set to execute each monday at 5 am. This process will not be executed when the atom is online again. It will be executed the following mondag if the atom is online at 5 AM. So you need to execute that manually.
Hope it answers your question.
just to clarify, is what you are describing when the atom is down/unavailable/turn-off, or when the platform reports that the atom is offline? I thought that the atom would still execute its scheduled processes even if it could not communicate with the platform. (so the platform would report it is offline)
In my experience both situations will cause scheduled processes not to execute.
That is not correct. The only time that schedules will not run is if the atom is truly not running. When the atom is unable to report its status to the platform (leading the platform to report the atom as "offline), it does not otherwise affect the running of the atom. All schedules, listeners, etc. will continue to function regardless of what the platform is reporting.
In that case I apologize for not correct answer.
Thanks for the response. Could you please elaborate this if the atom is truly not running? If my atom is local, and my network connectivity went down, then in that case, how the schedules will be run? I mean how the schedules will behave? What happens at that time and when the atom comes again online, means I got my network connectivity restored, how my older schedules will behave, what happens for them?
Sorry for these many questions at the same place.
Schedules are in no way tied to the platform or connectivity with the platform. All schedule information is held locally by the atom. The atom has an internal scheduler which launches executions according to their schedules.
Thanks James. One more question: So, to my schedule processes there would no effect in this case, but could I access process logs even my atom is offline?
And If my atom is online again, then all my executed processes logs/metadata would be reported to atom then and then I could see the logs,right?
Please correct me If I am wrong.
Thank you James for the quick turn around. I learnt new things. Thanks to all for your valuable responses.
Retrieving data ...