Quick Summary: If you click Full Refresh or Reprocess Data and nothing appears to happen, the request is usually in the processing queue.
How the Refresh Queue Works
When you click Full Refresh or Reprocess Data, the request is placed in a queue and processed as soon as capacity is available.
Starting the same action again before the previous batch has completed can queue more than one request. This is not recommended.
Factors That Affect Duration
A Full Refresh includes extraction from your ERP, transfer to the cloud, and processing into your instance of the app.
Typical duration is influenced by:
Size of your data set
Current load on your database server
Number of customer data sets being processed on the cloud servers at the same time
A Reprocess Data run processes data already synced to the cloud and does not pull new files from your ERP, but its duration still depends on how many customer jobs are running on the servers.
➜ For more on this topic, read: How To: Refresh the App With Your Latest Data
When You Should Not Start Another Refresh
You should avoid starting another Full Refresh or Reprocess Data if:
You have already triggered a batch and have not seen it complete
Users have been logged out with an update in progress message
If you think the app is taking too long to update, the correct action is to contact support, not to start additional refreshes.
Forget about these 👇 😞 😐 😃 Have your say here!