Azure / Azure/azure-functions-durable-js

An activity call to a non-existent function should error-out

Open
#197 2 comments 0 reactions 0 assignees View on GitHub
bug Enhancement
Dominant language
TypeScript
Stars
142
Forks
66
Avg merge
3d 19h
Merged PRs (30d)
4

Description

Currently, if we try to make an activity call to a non-existent function, the orchestrator simply sleeps indefinitely. We should instead validate that the function exists and error out if not.

Additionally, we should consider doing some basic typo-checking in case the function exists under a slightly different name. Think of `Hello` versus `Hello1`. The latter is a scenario that you can get into when using the plugin to create functions.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the orchestrator's activity-call handling and reproduce a call to a non-existent function to identify where it remains pending. Done means the call errors instead of sleeping indefinitely; investigate whether a nearby-name diagnostic such as Hello versus Hello1 can also be specified and tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.