ghost
commented
3 years ago Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @atpham256.
Issue Details
**Context** Currently, Stream Analytics Job `OutputStartMode` can only be set to `LastOutputEventTime` if the event has been processed before. Otherwise, the following error occurs: `"LastOutputEventTime must be available when OutputStartMode is set to LastOutputEventTime. Please make sure at least one output event has been processed. "` This means that the user needs to initially set `OutputStartMode` to `JobStartTime` and later to `LastOutputEventTime` if that's the desired behaviour. As a consequence, the config file responsible for deploying ASA job needs to be tweaked after the first deployment which is undesirable in the prod environment. **Proposed behaviour** The proposed behaviour is to default to `JobStartTime` when the user has chosen `LastOutputEventTime` setting and no event has been processed before. **Broken documentation formatting** Also, [the documentation](https://docs.microsoft.com/en-us/powershell/module/azurerm.streamanalytics/start-azurermstreamanalyticsjob?view=azurermps-6.13.0) is misleading and not properly formatted which may suggest the proposed behaviour: 
| Author: | amarek1 |
|---|---|
| Assignees: | - |
| Labels: | `Service Attention`, `Stream Analytics`, `customer-reported`, `feature-request`, `question` |
| Milestone: | - |
Context Currently, Stream Analytics Job
OutputStartModecan only be set toLastOutputEventTimeif the event has been processed before. Otherwise, the following error occurs:"LastOutputEventTime must be available when OutputStartMode is set to LastOutputEventTime. Please make sure at least one output event has been processed. "This means that the user needs to initially set
OutputStartModetoJobStartTimeand later toLastOutputEventTimeif that's the desired behaviour. As a consequence, the config file responsible for deploying ASA job needs to be tweaked after the first deployment which is undesirable in the prod environment.Proposed behaviour The proposed behaviour is to default to
JobStartTimewhen the user has chosenLastOutputEventTimesetting and no event has been processed before.Broken documentation formatting Also, the documentation is misleading and not properly formatted which may suggest the proposed behaviour: