I'm using the Create Collection task to create 6 collections over 3 different cosmos db accounts. This has functioned reliably for the past 12 months. Recently I will get a Resource Not Found error on 1 of the 6 collection creation tasks and the pipeline fails. The resource is clearly deployed - I probe the account to determine if the collection exists and set a condition that enables the creation task (creation task is skipped if the collection already exists). This feels like some sort of Azure issue.
Have you seen or heard reports of this?
tasklog_32.log
I'm using the Create Collection task to create 6 collections over 3 different cosmos db accounts. This has functioned reliably for the past 12 months. Recently I will get a Resource Not Found error on 1 of the 6 collection creation tasks and the pipeline fails. The resource is clearly deployed - I probe the account to determine if the collection exists and set a condition that enables the creation task (creation task is skipped if the collection already exists). This feels like some sort of Azure issue.
Have you seen or heard reports of this?
tasklog_32.log