Fix Power BI refresh failure (429 error) pulling data from Tovuti LMS API

Description: We run a training/course reporting system where each client has a separate Power BI report pulling course completion data from the Tovuti LMS API using Power Query (M). One of these reports has started failing with a 429 Too Many Requests error because the query re-fetches the entire history on every refresh, and that history has grown past Tovuti's API rate limit. We need someone to: Rewrite the Power Query so it pulls only new/updated records on each refresh, using the timestampModifiedAfter parameter on the courseProgresses endpoint (this parameter is already confirmed to exist and work), instead of re-pulling full history every time. Add retry/backoff logic so that if a 429 does occur, the query pauses and resumes instead of failing outright. Test the fix against our live Tovuti API and confirm the refresh completes successfully. Document the change briefly (what was changed and why) so we can maintain it going forward. Data model context: The report has 4 related tables: Teams, Courses, Users, and AssigmentsProgress (the fact table, pulled from Tovuti's courseProgresses endpoint, joined via teamId, courseId, userId). AssigmentsProgress is the table hitting the rate limit, since it grows every time someone starts, progresses, or completes a course. Requirements: Strong hands-on experience with Power Query (M language) and Power BI data refresh/incremental load patterns Experience working with REST APIs (pagination, date filters, rate limits, retry/backoff handling) Comfortable reading OpenAPI/schema documentation Clear communication in English Deliverable: Working, tested Power Query fix integrated into the existing report, with a short written explanation of the change. Budget: Fixed price for this task (amount to be discussed based on proposal) How to apply: Briefly describe your experience with Power Query incremental refresh and API rate-limit handling, and your estimated timeline for this fix.