Azure Stream Analytics job states

A Stream Analytics job could be in one of four states at any given time: running, stopped, degraded, or failed. You can find the state of your job on your Stream Analytics job's Overview page in the Azure portal.

Screenshot that shows job state.

State Description Recommended actions
Running Your job is running on Azure reading events coming from the defined input sources, processing them and writing the results to the configured output sinks. It's a best practice to track your job’s performance by monitoring key metrics.
Stopped Your job is stopped and doesn't process events. NA
Degraded There might be intermittent issues with your input and output connections. These errors are called transient errors that might make your job enter a Degraded state. Stream Analytics will immediately try to recover from such errors and return to a Running state (within few minutes). These errors could happen due to network issues, availability of other Azure resources, deserialization errors etc. Your job’s performance may be impacted when job is in degraded state. You can look at the diagnostic or activity logs to learn more about the cause of these transient errors. In cases such as deserialization errors, it's recommended to take corrective action to ensure events aren't malformed. If the job keeps reaching the resource utilization limit, try to increase the SU number or parallelize your job. In other cases where you can't take any action, Stream Analytics will try to recover to a Running state.
You can use watermark delay metric to understand if these transient errors are impacting your job's performance.
Failed Your job encountered a critical error resulting in a failed state. Events aren't read and processed. Runtime errors are a common cause for jobs ending up in a failed state. You can configure alerts so that you get notified when job goes to Failed state.

You can debug using activity and resource logs to identify root cause and address the issue.

Next steps