Billing question: Singleton orchestrators in the Consumption SKU

[mic-hnk]

Hello,

Let's assume I use singleton orchestrations with predefined IDs.

Does an attempt to schedule a new orchestration with an ID taken by another running orchestration count as an action in the Consumption SKU?

[mic-hnk]

bump @greenie-msft

[greenie-msft]

Hi @mic-hnk,

Apologies for the delay wtih responding.

The current definition of an action in the Consumption SKU, billing occurs when the Durable Task Scheduler dispatches a message that triggers execution (for example, starting an orchestration, activity, timer, or processing a result).
If an orchestration start is rejected because an instance with the same ID is already running, and no orchestration is started and no message is dispatched, then that attempt does not result in an action being billed.

[mic-hnk]

Thank you,

The docs are quite clear to be honest. I just wanted to be sure.