Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

  • Hi IA,

    I have an alphanumeric META point, that will only change state if the execution delay is 5 seconds or under.
    This appears to be a bug.

    Please see this post (EDIT: Go to post 6)

    I need to add an execution delay of 5 minutes.

    Many thanks

  • I suspect this has something to do with they context update of the meta point. Terry will be able to answer that but he will probably need more information on the meta point.
    context event type?
    update interval of the context point.

  • On the Meta point, "context event type" is - Update

    The point updating the context is a Virtual point, so I assume is instant.

    Here is the Meta data point:

                "script":"if(input1.value >= 28){\n    return \"Redlands Growth room 28 - Temperature HIGH\";\n}\nelse return \"Redlands Growth room 28 - Temperature NORMAL\";",
             "name":"Redlands Growth room 28 - Temperature",

    EDIT: This is my test setup:

    • A virtual numeric point

    • An alphanumeric meta point that reads the value of that point, with a script that returns a string depending on the script.

    • The Meta point has an execution delay, and the Meta point WILL NOT change state if the execution delay is over 5 seconds.

    if(input1.value >= 28){
        return "Redlands Growth room 28 - Temperature HIGH";
    else return "Redlands Growth room 28 - Temperature NORMAL";

  • I looked into this and I am able to get delays longer than 5 seconds but the max delay possible is the update interval of the context point. If you go to the administration --> system status --> work items you will see only one work item is created for each meta point XID: Meta delay for DP_b2fc2661-2f8a-4054-9d62-8e7224fef067. If the delay period is longer than the update interval then the old work item gets cancelled and a new one is created and scheduled for update time + delay.

  • I could see this being a new feature/change to the way it works. Instead of only having a single delay task we could have many. For example if your meta point is context updating every 1s and your execution delay is 1hr after 1hr of running you will have 3600 tasks sitting around with 1 executing every second after that. Execution delays were not really designed for that though as if you were to stop mango or that data source you would lose 3600 point values in the tasks that had not yet run.