Daily limits on outside services
Why a block can say that today’s limit for a service is reached, and what happens then.
Many blocks bring in data from services outside xMap Flows: traffic, weather and air quality, floods, charging stations, natural hazards, public tenders, xMap’s own places, jobs and population data, and xMap AI. Each of these services gives xMap Flows a plan with so many calls a day or a month, shared by every customer.
So that one busy flow, or one company, cannot use a whole plan up, each service has a daily limit for all of xMap Flows, and each organization may use a share of it a day. The limits are set by xMap and are well above what flows normally use.
- When a limit is reached, the block does not call that service for the rest of the day. Its step says so in plain words: Today’s limit for ... is reached for xMap Flows, or for your organization.
- Nothing is charged for a call that was not made. A block that already got part of its answer keeps it and says the rest was not asked.
- The run goes on as it does when a block fails: if the block is set to carry on when it fails, the rest of the flow runs; otherwise the run stops at it. Results are never made up to fill the gap.
- The count starts again at midnight UTC, and the next scheduled run goes ahead as usual.
If your flows need more of a service every day, book a call or write to us: xMap can raise the limit for your organization.