fix: treat timer triggers as external resume triggers

[radu-mocanu]

Summary

• skip timer resume triggers in the runtime polling loop
• keep timer triggers pending until Orchestrator resumes them externally

Depends on: UiPath/uipath-python#1767

Development Package

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

[project]
dependencies = [
  # Exact version:
  "uipath-runtime==0.11.5.dev1001370551",

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

[[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

Updates resumable runtime behavior so Timer resume triggers are treated as externally resumed (like API/Inbox), preventing the runtime’s auto-resume polling loop from attempting to read them at suspend time. This aligns timer-trigger handling with Orchestrator-driven resume semantics and bumps package versions accordingly.

Changes:

• Skip UiPathResumeTriggerType.TIMER in UiPathResumableRuntime._get_fired_triggers() polling/auto-resume checks.
• Update uipath-core dependency to >=0.5.23,<0.6.0 and bump uipath-runtime to 0.11.5.
• Regenerate uv.lock to reflect the dependency/version updates.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File	Description
uv.lock	Locks uipath-core to 0.5.23 and updates uipath-runtime metadata to 0.11.5.
src/uipath/runtime/resumable/runtime.py	Treats TIMER as an external resume trigger by excluding it from suspend-time polling.
pyproject.toml	Bumps project version and updates uipath-core minimum version constraint.

---

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

[sonarqubecloud]

Quality Gate failed

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

See analysis details on SonarQube Cloud