raushan2998

Hello @tokafew420, Thanks for the detailed explanation. This behavior occurs because RequestTelemetry is emitted before the monitor-triggered batch, due to MinEventBatchSize, gets processed. Since the Activity context isn’t updated in...

Hello @ogiel, Thanks for the detailed explanation. The root issue is that when deploying via WEBSITE_RUN_FROM_PACKAGE, Azure doesn’t automatically install packages listed in requirements.txt. This automatic installation only occurs when...

Closing the issue as there is no feedback.

Hello @yohny, Thanks for reporting. This happens because the Node.js v4 model doesn’t fully support single-entity table input binding with rowKey. It defaults to fetching all rows with the given...

Hello @yohny, Just a follow up regarding feedback on the above response provided from our side.

Thanks for confirming that the SDK works as expected. You’re not misunderstanding. In the current Node.js v4 programming model, the binding only filters by partitionKey, even if rowKey is specified....

Hi @yohny, Just a follow up regarding feedback on the above response provided from our side.

@yohny, Apologies for the confusion earlier. Just to clarify, In the current Node.js v4 programming model, even when both partitionKey and rowKey are set in the Table input binding, only...

Hello @nimbusnext-malhar, Thanks for the detailed info. Let me quickly address your questions: **1. How do we debug this?** First thing you can check is the Kudu console. Go to...

Got it. Thanks for the detailed testing. Since the bare function works across both plans, the platform and deployment flow seem fine. For Case 2, if functions aren’t showing up...