Matias Quaranta

@brettsam Yes it should, you would still receive a List/Array of documents but it would contain 1 element. Having said that, it might not be the best approach. The Trigger...

I understand what you mean, a couple of years ago I created this extension that works with the Queue trigger in batches: https://github.com/ealsur/WebJobs.Extensions.GroupQueueTrigger Maybe one day it's useful enough to...

Our extension code does not include any Retry behavior. This was already discussed at https://github.com/Azure/azure-webjobs-sdk-extensions/issues/783#issuecomment-1221139195 and it seems it was something Functions added on top of all Triggers.

@Thacai it is coming in the next major extension version https://github.com/Azure/azure-webjobs-sdk-extensions/pull/736, first preview will be out shortly

@v-anvari I have no insights on this scenario, never used Functions with MVC myself. Maybe @fabiocav or @brettsam might have any recommendations?

At least at this time, there is no Retry Policy support on the Cosmos DB extension that is built in or uses any of those configurations

If I understand the notice correctly, the retry policy is being removed from all triggers that currently support it: > The retry policy support in the runtime for triggers other...

@mpaul31 I don't understand what is the request here. Right now the Change Feed Trigger has no retry policy, so it never retries, how are you creating apps that have...

There is no code in the Cosmos DB Trigger or extension that reacts to `[ExponentialBackoffRetry(-1, "00:00:01", "00:00:10")]`. The Trigger code in fact has no error retry logic, here is where...

I don't know how that works, from the Trigger perspective, there is nothing that is blocking the checkpointing and moving forward if the execution of the code fails. Once the...