sqwishy

I might be misunderstanding but avoiding double counting time from flows is why the query includes `WHERE ... parent_job IS NULL` 🤔

I think what you're describing is technically more correct. But right now when you run a flow it says "ran in 1.234s" and if you look at your usage before...

@rubenfiszel immediately has a delay which implies it's not immediate but just a constant delay as opposed to exponential delay?

how about ``` json { "constant": { "seconds": 0 }, "exponential": { "multiplier": 1, "seconds": 0 } } ``` where exponential delay is calculated as `multiplier * seconds ^ failures`

Is there a workaround for this? _Edit:_ For now I have replaced `if="test"` with `if="(self=p[0]) && test"` or whatever the "correct" p index is, but I have no idea if...

I don't want nodes that failed the condition to end up in the document at all. I spend some time trying to figure out what the behaviour is for `for="data.variant"`...

I made a snippet to reproduce the issue and Peter on elmlang.slack.com made [an Ellie for it](https://ellie-app.com/dvMFPMNSj5ya1) so it's easy to see and play around with.

> * If rendering rows in a list, use css to flip the order of rows (display: flex, flex-direction: column-reverse) I wound up doing something along these lines. I gave...

I could be wrong, but it seems that row-level security policies are not enforced when a table is being accessed through a view. Instead, the table is accessed using the...

Looks like this was [already reported](https://github.com/zslayton/cron/issues/105) to the library back in May ... I'm not really familiar with cron syntax so it might be tricky for me to evaluate this....