Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CosmosDBTrigger does not accept any valid StartFromTime value #2882

Open
lostincomputer opened this issue Nov 28, 2024 · 0 comments
Open

CosmosDBTrigger does not accept any valid StartFromTime value #2882

lostincomputer opened this issue Nov 28, 2024 · 0 comments
Labels
Needs: Triage (Functions) potential-bug Items opened using the bug report template, not yet triaged and confirmed as a bug

Comments

@lostincomputer
Copy link

lostincomputer commented Nov 28, 2024

Description

CosmosDBTrigger does not accept any valid StartFromTime value and always fails with:

The listener for function 'Functions.Function1' was unable to start. Microsoft.Azure.WebJobs.Extensions.CosmosDB: The specified StartFromTime parameter is not in the correct format. Please use the ISO 8601 format with the UTC designator. For example: '2021-02-16T14:19:29Z'.

The exact same setup works in in-process model with Microsoft.Azure.WebJobs.Extensions.CosmosDB, but not in isolated worker model with Microsoft.Azure.Functions.Worker.Extensions.CosmosDB.

Steps to reproduce

Create an Isolated worker Azure function and reference Microsoft.Azure.Functions.Worker.Extensions.CosmosDB

[Function("Function1")]
public void Run([CosmosDBTrigger(
    databaseName: "databaseName",
    containerName: "containerName",
    Connection = "CosmosDbConnectionString",
    LeaseContainerName = "LeaseContainerName ",
    CreateLeaseContainerIfNotExists = true,
    StartFromTime = "2021-02-16T14:19:29Z" // Error is thrown even when I use the example value in the error message
    )] IReadOnlyList<Transaction> transactions)
{
}
@lostincomputer lostincomputer added the potential-bug Items opened using the bug report template, not yet triaged and confirmed as a bug label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Triage (Functions) potential-bug Items opened using the bug report template, not yet triaged and confirmed as a bug
Projects
None yet
Development

No branches or pull requests

1 participant