This problem is not uncommon on iPhones, so here's what you should do. If you are still experiencing this problem, you need to reboot your device. If this does not help, then try to clean the file cache because this sometimes makes a difference. The third option involves the use of services from priorityunlock.com, which has a cool ability to unlock devices. Personally, really helped me figure out my iPhone so that you can have success in this case. Try all the options and tell me what worked for you.
You describe a behavior that is more appropriate for a timer (an event that needs to happen at a specific time).
Schedule means a desirable situation from the activation of the schedule to the end.
Since there are events where a schedule behavior is not appropriate, as you say, i think the better solution is to add a checkbox to the schedule settings to indicate that is a "constant" schedule so even when the schedule is activated after the original start time the event handlers should be triggered.
@MattFox What it means is this:
The mangoNoSql module (IasTsdb) is trying to insert backdated values (that is values with timestamps which are older than those already contained in the series and saved to disk)
This is an expensive operation as it must rewrite the entire shard.
The TSDB queues the values in memory and tries to write them all out to the shard asynchronously.
Sometimes when this "backdate poster" thread tries to write the backdated values out the shard is already locked (due to a data source writing current values to the shard), resulting in messages like this.
No problem, I have committed a fix which will be included in the next Mango core release. The bug was in the core, not the module.
As an alternative work-around you could override or create a new email template .ftl file and replace the <@img logo="true"/> with <@img src="logo.png"/>
To create a new email template for your Excel report -
Copy the supplied template to your overrides, e.g. cp /opt/mango/web/modules/excelReports/resources/ftl/excelReports/reportEmailBody.ftl /opt/mango-data/overrides/ftl/excelReports/myTemplate.ftl
Edit your report to use the new template file
Hi Victor, Thanks for the feedback. I think all your points are very valid. We actually have plans to integrate into many services, as you mention, including Twillo, but our priority for Mango v4 has been stability and scale. We now have systems with over 1 million data points which was quite an achievement for Mango. But I completely agree, and we will not lose sight of these other features and integration.
Did you use the Twilio module in Mango v3? Did you find it worked well? It is possible we could upgrade the module to v4, but I was under the impression not many people used it, and it behaved a bit odd as a publisher rather than an event handler. Building it as an event handler will be the better way to go, but I welcome some more feedback.
You'll have to use the point-values api for the deletion though. ([mango_domain]/swagger-ui.html#/point-value-rest-controller/deletePointValuesUsingDELETE_1)
Refer to my http builder forum post here for using the http builder.
Let's call your context variable: pt
var DELTA_MAX = 10;
var last = pt.lastValue(1,false);
var delta = Math.abs(pt.value - last.value);
if(delta > DELTA_MAX)
I'm afraid I do not know if there are any other means at this time to delete point values without the API.