Activities get retried as their messages no longer exist

Open
#1,049 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, csharp
Domain
backend, distributed-systems

Research direction

Start by reproducing the orchestration described with HangRequest, the looping CheckStatus activity, and Service Bus progress messages. Trace the TaskScheduled#1 message lifecycle and the five-minute rescheduling behavior; done means completed orchestrations do not leave zombie CheckStatus activities or retry messages that no longer exist.

Written by the indexing model from the issue text.

Description

Hi,

I have a durable function that uses service bus to check on the progress of a process.

The orchestration basically does the following:

  • Calls activity "HangRequest".
  • "HangRequest" places an item in service bus and comes back to the orchestration
  • The orchestration then starts a loop where it calls another activity "CheckStatus"
  • "CheckStatus" looks for progress/completion messages from service bus.
  • The loop continues until we get a completion message from the service bus.

The problem we are seeing is that the CheckStatus activities are getting rescheduled to be run 5 minutes in the future. The message we are seeing look like this:

Failed to update or delete message [TaskScheduled#1] with ID = c4ceddc9-2288-4e78-a1cc-58b230398d7a because it no longer exists

The orchestration is actually able to complete but these zombie activities keep running for a while.

The HangRequest activity that is outside of the loop does not seem to have this issue. It's only the activities ran in the while loop that present this issue.

Dominant language
C#
Stars
1.7k
Forks
335
Avg merge
4d 2h
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/durabletask

All issues in Azure/durabletask

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.