Best approach for a robot that must run 24/7 seeing a website for changes

[David_Rodrigues]

Hi everyone,

I have a customer who needs a robot that should basically never stop running. The process requirements are:

• Continuously monitor a website for any changes
• If a change is detected, send an email notification

I’m not sure what the best UiPath setup would be for this kind of scenario.

• Should this be implemented using an Unattended Robot?
• Is it recommended to keep a dedicated machine running 24/7 for this robot?
• Or is there a better approach (e.g., triggers, Orchestrator queues, scheduled jobs, etc.) instead of having the robot always active?

Any guidance or best practices for building this type of always-on monitoring automation would be greatly appreciated.

Thank you all!

[Monali_Vekariya (Mona)]

Hi @David_Rodrigues

Don’t keep a robot running 24/7.
Use an Unattended robot scheduled from Orchestrator (for example every few minutes). Each run checks the website, compares with the previous state, and sends an email if there’s a change. This is more stable and the recommended approach.

[MohammedShabbir]

I would not recommend keeping a robot running 24/7 for monitoring scenarios. You can use an Unattended Robot triggered by Orchestrator schedules (for example, every few minutes).

Each execution reads the required website data, compares it with a previously stored state (using an Orchestrator Asset, file, Storage Bucket, or database), and sends an email if a change is detected. You can also store snaps in the last run and then compare this with current run.

The comparison can be also done using a simple If condition for text or Compare Data Tables for tabular data.

[David_Rodrigues]

Oh! I didn’t see that as a possibility!

Thank you so much for your response, i will try to make it!

[David_Rodrigues]

Oh i see, i’ve never touched the Orchestrator that much to use it as an Asset but i will try my best! Thank you so much for the response!