Inbound Flow Fetch Frequency Offset
Adrian Duyzer
An inbound flow can now run at a minute you choose within its cycle instead of only on the clock boundary, and 15 minutes is a new frequency on paid plans.
Impact: nothing changes for existing flows. They keep an offset of :00 and run at the same minutes as before. Set an offset when a VAN or a trading partner asks you not to on the top (e.g. 14:00), quarter (e.g. 14:15) and half (e.g. 14:30) of the hour, which is when everyone tends to connect to them. The setting is Offset, under Frequency, on the partner’s Flows card and on the flow’s edit form.
How the offset works:
- A flow set to 15 minutes with an offset of :08 runs at :08, :23, :38 and :53. A 60-minute flow with an offset of :37 runs at :37 only.
- The offset is always less than the frequency. Changing the frequency in the app sets the offset back to :00.
- Minutes are counted in UTC. That differs from your clock only if your time zone is 30 or 45 minutes off the hour.
- A paused flow keeps its offset, and so does a flow you rebuild.
GET /platform/flowsand the MCPflow_listandflow_gettools return the offset asscheduleOffsetMinutes, next tofrequency.
Limits:
- The offset moves the scheduled fetch only. An outbound document still uploads as soon as you submit it, so uploads can reach the partner’s server at any minute.
- New flows start at :00. We do not spread flows across the hour for you.
- The Developer plan stays at 60 minutes or paused. It can use an offset.
The settings are described in the flows docs.
This update was written with AI assistance. It has been reviewed and edited by a human.