Sequelize adding ORDER BY to subquery and main query causing ER_BAD_FIELD_ERROR

What you are doing?

When I add these two scopes, my publishedAt order gets added twice, once to the subquery (which is what i want), and once to the encasing query which causes a ER_BAD_FIELD_ERROR

FIELD_ERROR: Unknown column ‘Ticket.published_at’ in ‘order clause’

If I remove it from the outer query, the query works as expected, so my question is why would it be being added to both queries?

// Scope 1
published: function() {
 var data = {
   where: {
     status: 'published',
     publishedAt: {
       $lt: models.sequelize.fn('NOW')
     }
   },
   order: [
     ['publishedAt', 'DESC']
   ]
 };

 return data;
},


// Scope 2
decorated: function() {
  var includes = {
    include: [{
      model: models.Asset,
      as: 'FeaturedAsset'
    }, {
      model: models.Category
    }, {
      model: models.User,
      as: 'Author'
    }]
  };

  return includes;
}

What do you expect to happen?

I wanted it to order the inner query

What is actually happening?

It added the order to both inner and outer query.

SELECT ... FROM (
    SELECT ... FROM `tickets` AS `Ticket` WHERE (`Ticket`.`deleted_at` IS NULL AND (`Ticket`.`status` = 'published' AND `Ticket`.`published_at` < NOW() AND `Ticket`.`channel_id` = 3)) 
    ORDER BY `Ticket`.`published_at` DESC LIMIT 0, 6) AS `Ticket` ... 
ORDER BY `Ticket`.`published_at` DESC;

Dialect: mysql Database version: 5.6 Sequelize version: latest

[psyanite]

http://docs.sequelizejs.com/manual/querying.html#ordering

[elias-summermatter]

Same problem here! Someone has a solution?