Rulings

• 2015-02-25
  Casting the card again due to the delayed triggered ability is optional. If you choose not to cast the card, or if you can't (perhaps because there are no legal targets available), the card will stay exiled. You won't get another chance to cast it on a future turn.
• 2015-02-25
  If a spell with rebound that you cast from your hand is countered for any reason (either because of another spell or ability or because all its targets are illegal as it tries to resolve), that spell won't resolve and none of its effects will happen, including rebound. The spell will be put into its owner's graveyard and you won't get to cast it again on your next turn.
• 2015-02-25
  At the beginning of your upkeep, all delayed triggered abilities created by rebound effects trigger. You may handle them in any order. If you want to cast a card this way, you do so as part of the resolution of its delayed triggered ability. Timing restrictions based on the card's type (if it's a sorcery) are ignored. Other restrictions, such as "Cast [this spell] only during combat," must be followed.
• 2015-02-25
  As long as you cast a spell with rebound from your hand, rebound will work regardless of whether you paid its mana cost or an alternative cost you were permitted to pay.
• 2015-02-25
  If you cast a spell with rebound from any zone other than your hand (including your opponent's hand), rebound will have no effect.
• 2015-02-25
  If a replacement effect (such as the one created by Rest in Peace) would cause a spell with rebound that you cast from your hand to be put somewhere other than into your graveyard as it resolves, you can choose whether to apply the rebound effect or the other effect as the spell resolves.
• 2015-02-25
  Rebound will have no effect on copies of spells because you don't cast them from your hand.
• 2015-02-25
  If you cast a card from exile this way, it will go to its owner's graveyard when it resolves or is countered. It won't go back to exile.
• 2017-11-17
  Ojutai's Breath can target a creature that's already tapped. It still won't untap during its controller's next untap step.