Hello, I have a question regarding the accounting of payloads, in application workflows with the exception of triggers: endpoint, timer and virtual button, the others also count payloads when they are executed, or when an execution is triggered from these triggers it is not counted a payload?
Thanks
Hi @Vander_Maziero,
For your awareness, we do have updates planned to improve our documentation around this topic, but in the meantime, you can expect the following interactions to count as a payload:
As you mentioned, most of these are from Trigger Nodes. However, creating events (Event Data Nodes), data requests (HTTP Node), webhook replies (Webhook Reply Node), workflow runs triggered by other workflows (Workflow Trigger Node), and data table manipulations (Data Table Nodes) do not count as a payload.
However, there are some non-trigger nodes that can generate a paylaod. For example, the Device State Node is an Output Node. Because this node reports state, and that’s one of the action that Losant’s counts as a payload, this is an example of a non-trigger node generating a payload.
Is there a particular node type in your application workflow that you are concerned about impacting payload count?
You can see further details regarding payload counts and usage statistics in your Organizations overview page.
Thanks,
@Aidan_Zebertavage
So, if I use this flow, trigger by Device: Inactive, and create an event from that, a payload would not be counted, correct?
Your workflow above would increase your payload count by one because of the Device: Inactive trigger node itself, and not the Build Event or Event: Create nodes in the workflow.
The Device: Inactive trigger node will create a payload that includes the date of the last state report in the data field, as well as the duration of inactivity.
This payload is then used throughout the rest of the workflow to build and create your event, but those two remaining nodes will not increase your payload count, since they are ingesting and processing information off the payload generated by the Device: Inactive node.
Thanks,
@Aidan_Zebertavage
Thanks, @Aidan_Zebertavage
So, looking at the API schema (https://docs.losant.com/rest-api/schemas/#payload-counts) that returns the payload count, what property is that payload counted in, or that payload count isn’t in the schema?
The Device: Inactive trigger nodes payload counts are rolled into the - timer.flow counter.
We do not separate out this particular node into its own counter.
Thanks,
@Aidan_Zebertavage
Another question about the payload counts of the trigger nodes, I tested in the sandbox, the following flow, and noticed that the triggers Device: State and Event, are not counted in the payloads, right?
Because in the payload count, the virtual button (5), the set device state by workflow (5), and the states sent via simulator (5) were counted. The other triggers are not accounted.
Hey @Vander_Maziero,
Apologies on the delay, you are correct on both nodes, the Device: State trigger does not generate a payload itself.
The device reporting state generates that payload, so it’s already been accounted for.
The Event: Create node also does not generate a payload, rather it is creating an Event based on information from a previously generated payload.
Thanks,
@Aidan_Zebertavage
