linkedin / linkedin/iris

Handling User busy conditions

Open
#546 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
845
Forks
146
PR merge metrics
No merged PRs in 30d

Description

I have configured plan which has two steps.

**Plan Details:**
In step1, I have scheduled the call for two persons ( Retry-2).
In step2, I have scheduled the call for one persons (Retry -2).

In step1, When both persons are busy (In other call), I need to skip the step1 immediately without doing any retry and go for step2 escalation.

This will avoid unnecessary delay and save my time on this specific condition.

Is there any way to achieve this logic?.

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points. Start by tracing plan execution for a step with multiple recipients and retries, then determine how a busy result should bypass retries and advance to the next escalation step; done means this behavior is implemented and verified without delaying on the configured retries.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.