@Isa that sounds like a different issue - are you sure the instance remains in 'Scheduling' because of RabbitMQ timeouts, or is there something else in the logs?
@Isa that sounds like a different issue - are you sure the instance remains in 'Scheduling' because of RabbitMQ timeouts, or is there something else in the logs?