Once you complete a Task (check its checkbox) it is saved to the database and is secure. But sometimes Tasks disappear! Why is that?


Tasks might disappear (or, technically, change dates) if you change an aspect of Crop's cycle so one (or more) of its Task dates change.


Here is an example:

  • You complete a Sowing Task for your Sunflower Crop on May 3 for Harvest on May 12.

  • Then you edit the Crop and change its Days to Maturity (DTM) from 9 days to 8 days.

  • This change would shift the Sowing Task from May 3 to May 4, while the Harvest date would stay the same.

  • You would then see a new Sowing Task on May 4, that is not completed.

  • In this situation, there are two things to know:

    • The original Sowing task from May 3, which you already completed, is still saved to the database

      • If you were to change the Crop's DTM back to 9 days, you would see the original completed Task back in place! 

    • You should not complete the new Task generated for May 4 or this will create a duplicate entry in your Report.

      • The duplicate report entry would have the same Crop and Harvest Date, but with a different Sowing date.

        • As a note, it is "impossible" for the same Crop to show up more than once in a Report for a single Harvest date


If one of your Tasks changes due to a Crop change, but the Task has not been completed, then the crop change is inconsequential to your Reports.



Other Task Changes


Other changes to a Crop's properties could also result in Task changes. Again, if the Task has already been completed, the displayed Task changes will not affect your records. For example, changing a Crop's Yield could change the number if trays displayed your Tasks for that Crop.