# You may currently need to call backends explicitly when using Plots

**URL:** https://discourse.julialang.org/t/you-may-currently-need-to-call-backends-explicitly-when-using-plots/4302
**Category:** Visualization
**Created:** [June 16, 2017, 12:07pm UTC](https://discourse.julialang.org/t/you-may-currently-need-to-call-backends-explicitly-when-using-plots/4302 "2017-06-16T12:07:55Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![mkborregaard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkborregaard/32/556_2.png) [@mkborregaard](https://discourse.julialang.org/u/mkborregaard)
#### Post date: [June 16, 2017, 12:07pm UTC](https://discourse.julialang.org/t/you-may-currently-need-to-call-backends-explicitly-when-using-plots/4302/1 "2017-06-16T12:07:55Z")

</div>

Not sure where to put this package-specific announcement, but I figured it would save some people a headache to make it visible.

Since the change to 0.6 there is a persistent issue with world age in Plots, particularly when using the new Juno version.  
The solution is in each case to call the backend explicitly, e.g. `using Plots; gr()` – (or `pyplot()`, `plotlyjs()`, `plotly()`, `pgfplots()`, `unicodeplots()`, `glvisualize()`, `inspectdr()`, whichever suits your needs and taste the best - or simply, as a general solution, `backend()`). This should be a temporary workaround only.