Loading Policy

The minimum interval between one charge and another is 15 minutes;

The maximum execution time of a charge is 90 minutes, that is, 1h30min. This means that, regardless of whether the load is total or incremental, this is the maximum time it will be in the queue. After this period, the "timeout" occurs, the load is interrupted and does not run again until there is a new schedule, giving way to the next one in the queue;

Editing structures count as total loads;

It is only possible to have a load schedule in the "Interval" mode per structure;

Projects of type "Demo", "Approval" and "Template" cannot have a data load schedule, send schedule or KPI monitoring (it is not allowed to save new schedules);

Daily loads have a higher priority level than Interval loads during the execution queue, that is, it has preference;

The load scheduling time does not mean that the load will run at this time. For example: If you made a schedule to run at 8:00 am, your schedule might run at 8:10 am, since you scheduled loads to run every 15 minutes that do not have priority in the execution queue;

Each time a load is executed, the cache is cleared, as the system will have to consult the database again and when it performs this query, the cache is cleared, that is, if your project structure has many load schedules per day, the longer it will take you to access your information, such as accessing analyzes and dashboards, since with each load it is necessary to consult the bank again in search of updated information. The cache is only generated when the object is opened.