Surface duplicate service bus action runs in the monitoring UX

[rllyy97]

Priority

P3 - Medium (Nice to have)

Feature Area

Monitoring/Run History

Problem Statement

Writing on behalf of customer

Currently, service bus actions are executed "at least once" by design, and there is no indication in the monitoring view UX that an action has executed more than once.

Proposed Solution

We ideally should show some sort of information in the UX if an action executed more than once.

Alternatives Considered

No response

Which Logic App type(s) should this apply to?

Both

Additional context

No response

[github-actions]

AI Triage Analysis

Area: Monitoring / Run History | Priority: P3 (Medium) | SKU: Both (Consumption + Standard)

Implementation Scope

• libs/designer/src/lib/ui/panel/nodeDetailsPanel/tabs/monitoringTab/propertiesPanel.tsx — renders the Properties section for a node's run; currently shows start/end time, status, and tracking IDs but does not surface repetitionCount
• libs/logic-apps-shared/src/utils/src/lib/models/logicAppsV2.ts:L1015 — WorkflowRunAction already has repetitionCount?: number and iterationCount?: number fields in the model
• libs/logic-apps-shared/src/designer-client-services/lib/standard/run.ts & .../consumption/run.ts — getRepetitions() and getScopeRepetitions() APIs already exist to fetch per-action repetition records
• libs/designer/src/lib/ui/MonitoringTimeline/hooks.ts — useTimelineRepetitionCount already handles timeline-based repetitions; similar pattern could be adapted for service bus at-least-once runs

Architecture Notes

The repetitionCount field is already present on WorkflowRunAction and populated by the backend for at-least-once scenarios. The most targeted path would be to expose this field in PropertiesPanel.makeValuesFromOperationProperties() when its value is > 1, alongside an informational message. For a richer UX (showing each individual execution's inputs/outputs), getRepetitions() could drive a list view — following the same pattern used for scope/loop repetitions today.

Complexity Estimate

Low–Medium — The data is already in the model and services exist. The main work is UI: conditionally rendering a "ran N times" indicator in PropertiesPanel (Low), or building a full repetition-selector UI similar to loop iteration handling (Medium).

---

Automated analysis by issue triage agent. May contain inaccuracies — verify before acting.
Calibration: reviewed 0 past triages (search returned no prior comments), 0 corrections applied.

Generated by Issue Triage Agent for Azure Logic Apps UX for issue #9026 · ◷