Hi ggonong,
Thank you for posting query in Microsoft Q&A Platform.
It is possible that the delay in output is due to the large time window of 7 days. When a Stream Analytics job starts, the input events are read. But, there can be a delay in the output, in certain circumstances. Large time values in temporal query elements can contribute to the output delay. To produce the correct output over large time windows, the streaming job reads data from the latest time possible to fill the time window. The data can be up to seven days past. No output produces until the outstanding input events are read. This problem can surface when the system upgrades the streaming jobs. When an upgrade takes place, the job restarts. Such upgrades generally occur once every couple of months.
One mitigation for this kind of first output delay is to use query parallelization techniques, such as partitioning the data. Or, you can add more Streaming Units to improve the throughput until the job catches up.
You can also check the following:
- Check if the input data is being received by the Stream Analytics job. You can do this by checking the input metrics in the Monitoring section of the Stream Analytics job.
- Check if the output data is being written to the Cosmos DB. You can do this by checking the output metrics in the Monitoring section of the Stream Analytics job.
- Check if there are any errors in the job. You can do this by checking the job logs in the Monitoring section of the Stream Analytics job.
If you are still unable to resolve the issue, please provide more information about the job and the input data so that I can assist you better.