# `mix geo_genius.rollback`
[🔗](https://github.com/agoodway/geo_genius/blob/main/lib/mix/tasks/geo_genius.rollback.ex#L1)

Rolls a collection's publication back to its previous release.

## Options

  * `--collection` - the collection to roll back (required)
  * `--yes` - actually perform the rollback
  * `--repo` - the Ecto Repo to run against
  * `--prefix` - the PostgreSQL schema GeoGenius is installed in

A rollback changes what every host reading this collection sees, so like
`mix geo_genius.uninstall` it prints what it would do and does nothing
without `--yes`. It does not happen from a typo.

A rollback that committed exits zero even when the release it rolled back to
could not be read afterwards. The publication has already moved by then, so
exiting non-zero under a "failed" label would invite a deploy script that
retries on exit code to roll the collection back a second step. The
unreadable outcome is reported on stderr instead, naming the rollback as
done.

---

*Consult [api-reference.md](api-reference.md) for complete listing*