You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If it's low impact, the API can be used to report the progress back to the user.
Pipe dream would be to have a progress graph with the domains / time plotted over time and the estimate based on last X measurements.
Re-fetching the status can be done based on the progress, e.g. with a minimal of one per hour, and a maximum of one per minute. This could remove a lot of API calls (although heavier for sure) and give more progress information to the user.
The text was updated successfully, but these errors were encountered:
Let's first wait for the impact of using the progress in the Batch API.
If it's low impact, the API can be used to report the progress back to the user.
Pipe dream would be to have a progress graph with the domains / time plotted over time and the estimate based on last X measurements.
Re-fetching the status can be done based on the progress, e.g. with a minimal of one per hour, and a maximum of one per minute. This could remove a lot of API calls (although heavier for sure) and give more progress information to the user.
The text was updated successfully, but these errors were encountered: