Skip to content

feat: support for IS resume triggers#105

Open
GabrielVasilescu04 wants to merge 1 commit intomainfrom
feat/add-support-for-inbox-triggers
Open

feat: support for IS resume triggers#105
GabrielVasilescu04 wants to merge 1 commit intomainfrom
feat/add-support-for-inbox-triggers

Conversation

@GabrielVasilescu04
Copy link
Copy Markdown
Contributor

@GabrielVasilescu04 GabrielVasilescu04 commented Apr 22, 2026

Description

Support for inbox triggers

Development Package

  • Add this package as a dependency in your pyproject.toml:
[project]
dependencies = [
  # Exact version:
  "uipath-runtime==0.10.3.dev1001050414",

  # Any version from PR
  "uipath-runtime>=0.10.3.dev1001050000,<0.10.3.dev1001060000"
]

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

@GabrielVasilescu04 GabrielVasilescu04 self-assigned this Apr 22, 2026
@GabrielVasilescu04 GabrielVasilescu04 force-pushed the feat/add-support-for-inbox-triggers branch 3 times, most recently from 49cd268 to 4dc93c9 Compare April 24, 2026 14:22
@GabrielVasilescu04 GabrielVasilescu04 marked this pull request as ready for review April 30, 2026 08:22
@GabrielVasilescu04 GabrielVasilescu04 requested a review from a team as a code owner April 30, 2026 08:22
Copilot AI review requested due to automatic review settings April 30, 2026 08:22
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds Integration Services “Inbox” resume-trigger support to the resumable runtime by treating Inbox triggers as async-external (similar to API triggers) during the auto-resume polling phase, and exposes the related trigger type via runtime re-exports.

Changes:

  • Skip INBOX triggers (along with API) when checking stored triggers for immediate auto-resume after suspension.
  • Add a regression test ensuring read_trigger is not called for Inbox triggers during the auto-resume check.
  • Re-export UiPathIntegrationTrigger and bump package version to 0.10.2.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
src/uipath/runtime/resumable/runtime.py Updates auto-resume fired-trigger polling to exclude INBOX triggers and adjusts docstring.
tests/test_resumable.py Adds coverage for “Inbox triggers must not be polled pre-resume”.
src/uipath/runtime/resumable/trigger.py Re-exports UiPathIntegrationTrigger for backward compatibility.
src/uipath/runtime/resumable/__init__.py Re-exports UiPathIntegrationTrigger from the resumable package.
src/uipath/runtime/__init__.py Re-exports UiPathIntegrationTrigger from the top-level runtime package.
pyproject.toml Bumps package version to 0.10.2.
uv.lock Updates the editable package version entry to 0.10.2.
Comments suppressed due to low confidence (1)

src/uipath/runtime/resumable/runtime.py:155

  • The docstring says this returns a resume map for fired triggers or None, but when triggers exist and all are skipped (e.g., only API/INBOX), the method can still end up returning an empty dict via _build_resume_map([]). Consider returning None when there are no pollable triggers / when the built resume map is empty, or update the docstring to mention the empty-dict case.
        Returns:
            A resume map of {interrupt_id: resume_data} for fired triggers, or None.
        """

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

Comment on lines +163 to +164
if t.trigger_type
not in (UiPathResumeTriggerType.API, UiPathResumeTriggerType.INBOX)
@GabrielVasilescu04 GabrielVasilescu04 force-pushed the feat/add-support-for-inbox-triggers branch 6 times, most recently from 0e16bbb to 721c429 Compare April 30, 2026 10:56
@GabrielVasilescu04 GabrielVasilescu04 force-pushed the feat/add-support-for-inbox-triggers branch from 721c429 to da349db Compare April 30, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants