Nico Korthout

I've marked this `severity/high` but it could be considered `severity/critical` as the deployment partition is blown after this happens. I've marked it as high because no stable release has been...

@remcowesterhoud Are you on `8.1.0-alpha4`? Perhaps something changed in the meantime.

We shouldn't throw an IllegalArgumentException, because that would be an unexpected error. Instead we should handle the error by rejecting the command.

Thanks for reporting @falko. For completeness, an [error](https://console.cloud.google.com/errors/CM7W292E08KuWQ?service=zeebe&time=P7D&refresh=off&project=camunda-cloud-240911) was also reported for the thrown exception in google cloud.

Relates to https://github.com/camunda-cloud/zeebe/issues/3098

IllegalStateException thrown at: [FlowElementInstantiationTransformer.java#L94](https://github.com/camunda-cloud/zeebe/blob/1.2.4/engine/src/main/java/io/camunda/zeebe/engine/processing/deployment/model/transformer/FlowElementInstantiationTransformer.java#L94)

Happened again, see https://github.com/camunda/zeebe/pull/9935#issuecomment-1201175501 ``` Error: Tests run: 12, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 270.506 s

Thanks @deepthidevaki Sorry to have to open this one again 🙇 But thanks for looking into it.

@saig0 It's easy to come up with an example that requires all intervals to have had a trigger at some point. For example, a business process to send some amount...

@felix-mueller This behavior differs from C7, but it might be considered an improvement. For others (although I can't come up with use cases), it might come as a surprise. Can...