Treat timer triggers as external resume triggers

[radu-mocanu]

Timer resume triggers are completed by Orchestrator after the job suspends. The resumable runtime should persist them and let Orchestrator handle the wake-up instead of polling them immediately in the same process, which can self-resume before the job ever reaches Suspended.

Development Package

• Add this package as a dependency in your pyproject.toml:

[project]
dependencies = [
  # Exact version:
  "uipath-runtime==0.11.4.dev1001360546",

  # Any version from PR
  "uipath-runtime>=0.11.4.dev1001360000,<0.11.4.dev1001370000"
]

[[tool.uv.index]]
name = "testpypi"
url = "https://test.pypi.org/simple/"
publish-url = "https://test.pypi.org/legacy/"
explicit = true

[tool.uv.sources]
uipath-runtime = { index = "testpypi" }

[Copilot]

Pull request overview

Adjusts the resumable runtime’s post-suspension auto-resume behavior so timer-based resume triggers are treated like external (Orchestrator-driven) resume triggers, preventing the runtime from polling and potentially self-resuming before the job is actually suspended in Orchestrator.

Changes:

• Updates _get_fired_triggers() documentation to include Timer triggers in the “external trigger” category.
• Excludes UiPathResumeTriggerType.TIMER from the set of triggers eligible for immediate polling/auto-resume right after suspension.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate failed

Failed conditions
75.0% Coverage on New Code (required ≥ 90%)

See analysis details on SonarQube Cloud

[radu-mocanu]

Closing in favor of the split runtime PR stack starting at #137.