The following runs are missing variables and are hence not shown

#1

Hi Will,

We are running into this problem. After saving some runs, the runs are shown in the linegraphs. After logging out/logging in or refreshing the browser the saved runs are still shown, but at a random moment the saved runs are not visable anymore. Following message apears:

4 runs not shown:
The following runs are missing variables and are hence not shown.

*** Scenario A**
*** Scenario B**
*** Scenario A**
*** Scenario B**

We have checked all variables double and there are no missing variables.
Can you support us at this point?

Link to project: https://forio.com/app/circulair-beton/circulait-beton/index.html#betonvraag2~rcomp.html

Regards Jan

#2

Hi Jan –

It sounds like the runs are timing out from memory. The specific graphs being viewed must be saved to the database to be viewed once the run exits memory.

Can you check this file and make sure the variables you wish to see are listed with the “save” property as true?

https://forio.com/epicenter/circulair-beton/circulait-beton/model/blob/circular-dynamics-bouw-02.ctx2

WILL

#3

Hi Will,
It seems that completing the ctx file solved the problem. Thanks!

Maybe you can give me some support on some other things:

The state of the input sliders on the decisionpage are stored in a cookie. Is it possible to overrule the cookie and bring the decisionpage sliders in the state of a saved run. I have experimented with the ‘getRun’, ‘load’, and ‘run strategie’ functions in the Forio documentation, but the decisionpage holds the state of the cookie. Only clicking ‘reset’ wil let the decesionpage return to the baseline settings.

The idea is that endusers can make adjustments on a saved run (Scenario). Therfore the have to can bring back the decisionpage in the state of a saved run and save the made adjustments. An example of wat we want to accomplish can you see on top right of the decesionpage. Clicking on a saved Scenario should set the state of the sliders in the state of the saved run-id. Changes should be saved in the specific runid.

In short: We only need the ‘saved’ runs with the possibility to retrieve a saved run and save adjustments in this specific run. In most cases, endusers will use/edit max. 5 saved runs. We don’t need the automatic creation of runs in the runmanager. It creates big amount of runs we don’t need. Possible it slows down the system?

I hope you can give some insights on this.

Regards en thanks!
Jan

#4

Hi Will,
I am planning to make a script that by logging cycles trough all runs and removes all runs, except the runs with the flag ‘saved’, so the system stays clean and runs we don’t need are deleted. Do you think thats the right way to work? Or is there a simpler way to do that or is this automaticaly done by Forio?
Regards Jan

#5

Hi – there’s no automatic function for this.

Runs are cleared from memory automatically after a period of time (default is 30 min). But the run can be retrieved in a list of runs after. If you want to clean this out, loop through the runs as you suggest and set the “trashed” field.

WILL