Trigger delay issue

Feedback Orchestrator
,
1

Hi UiPath Community,

I’m facing an issue where my event trigger in Orchestrator is delayed by 2 to 3 hours. The job does not start at the expected time, even though the trigger is configured correctly.

Details:

  • Platform: UiPath Cloud Orchestrator (Community)
  • Trigger Type: Event-based (Schedule Trigger)
  • Robot Type: Unattended
  • Machine and Robot: Connected, licensed, and showing as available
  • Time Zone: Verified as correct in both Orchestrator and Trigger settings
  • No long-running jobs are blocking the execution
  • No issues seen in job logs, just a huge delay between scheduled time and actual job start

I’ve already tried:

  • Rechecking CRON/time zone
  • Verifying robot and machine status
  • Confirming there are no previous stuck jobs

Still, the delay persists.

Has anyone else experienced this delay? Any help or guidance would be appreciated!

Thanks,
Nidhin Gopinath

3

Hi @Nidhin_Gopinath

Welcome to UiPath,

Could you pls share the screenshot of trigger , might be we can help you better.

Happy Automation

4

@Nidhin_Gopinath

Are you seeing this delay always? or is it intermitent?

when you say delay is it stuck in pending or the trigger does not happen itself?

did you try creating a new trigger?

cheers

5

The image shows the UIPath Integration Service interface for a shared payment bot, detailing its HTTP webhook connector, event monitoring, and input argument settings with fields for connector, connection, event, and data filters. (Captioned by AI)
The image shows the UIPath Integration Service interface for a shared payment bot, detailing its HTTP webhook connector, event monitoring, and input argument settings with fields for connector, connection, event, and data filters. (Captioned by AI)1838×890 95.7 KB

6

Is the actual time the process start, always exactly after the original expected time?
Check Time zone of orchestrator, per organization.

Delete and recreate trigger.

Ensure machine the process needs to run on is not blocked by other process.

7

yes i tried creating new trigger but did not work, the delay is happening after a event that is suppose to trigger the workflow (via webhook) has happened. It is taking almost 2 - 3 hrs to execute the workflow in studio, also it has only happened today, till yesterday the overall trigger automation was working fine.

8

@Nidhin_Gopinath

if its a webhook trigger then one it is preview there might be some sisue

second the calling agent also must have called it with a delay

cheers