Hi, I’m working through N8N102 - Section 1 (API Integration Pipeline) and stuck on the final checkpoint. My FinalizePipeline node sends this payload to /course/n8n102/finalize: { “total_orders”: 50, “enterprise_count”: 12, “batch_size”: 10, “retry_enabled”: true } I get back a 422 error: “I…

Hi @muktern8n Welcome! The error names your counts, not your progress, so this is the payload rather than stale backend state. batch_size is the one value that doesn’t match Step 2.7, which uses 5. Set BatchPriorityOrders to a batch size of 5, re-run the whole workflow in one go, and finalize with b…

@muktern8n You can find the answer here! [image] : FinalizePipeline endpoint returning "Invalid final data counts" — Section 1, Step 2.7 ello, Batch should be 5. Counts are here in the screenshot. [screenshot 2026-07-28 at 12.49.29] Please ensure your data types are correct. total_orders : …

Adding to what Anshul said, since there is a thread with your exact error message (not the “Progress incompleted” one) where Jamie from the n8n team confirmed the batch size and posted a screenshot of the reference run: [image] : FinalizePipeline endpoint returning "Invalid …

Hi @muktern8n I think the issue is the batch_size. For the final checkpoint, it should be 5, not 10. Your other values look right: { “total_orders”: 50, “enterprise_count”: 12, “batch_size”: 5, “retry_enabled”: true } I’d change BatchPriorityOrders to a batch size of 5, then run the complet…

Thanks Subham, batch_size: 5 was indeed the fix, and SendToPriorityQueue now runs successfully (all batches green, 12 items confirmed). However, FinalizePipeline is now back to a different error: “Progress incompleted. You have not completed all steps in this assessment.” This is confusing because …

@muktern8n A backend check isn’t needed, the flaw is in your flow. You listed orders quqed as 50, as proof step 1 sucseeded, however, in another thread, this was said the step 1 part wants only 10, so you need to disable pagnation. [image] N8N102 Section 1 Hands-on Exercise: Building an API Integ…

Thanks for the reply, but I think this might not be correct — the course document explicitly says in Step 2.1-2.2 that pagination should return 50 orders, and the confirmation code for that checkpoint literally contains “PAGED-ORDERS-QUEUE” in its name, which I received successfully. The rest of the…

@muktern8n This is the link @jamiemadden_n8n is the official academy helper, so what he said should work! [image] N8N102 Section 1 Hands-on Exercise: Building an API Integration Pipeline - FinalizePipeline 持續回傳「Progress incompleted」 N8N102: Integrations: APIs and Connec…

Section 1 finalize retourne 422 « Invalid final data counts » malgré une charge utile correcte

Questions

achamm Août 23, 2026, 3:09 3

@muktern8n Tu peux trouver la réponse ici !

Sujet		Réponses	Vues
N8N102 Section 1 hands-on: finalize returns 422 "Progress incomplete" / "Invalid final data counts" N8N102: Integrations: APIs and Connected Workflows	2	32	Octobre 5, 2026
: FinalizePipeline endpoint returning "Invalid final data counts" — Section 1, Step 2.7 N8N102: Integrations: APIs and Connected Workflows	3	114	Juillet 28, 2026
Requesting verification or a reset of your backend progress records for the N8N102 Section 1 API Integration Pipeline assessment, because despite your workflow being correctly configured and executed, the final checkpoint call to /finalize keeps returnin Questions	1	60	Août 24, 2026
N8N102 Section 1 Hands-on Exercise: Building an API Integration Pipeline - FinalizePipeline 持續回傳「Progress incompleted」 N8N102: Integrations: APIs and Connected Workflows	6	292	Juillet 21, 2026
N8N102 Section 1 FinalizePipeline returns "Missing required parameter: total_orders" N8N102: Integrations: APIs and Connected Workflows	1	105	Août 18, 2026

Section 1 finalize retourne 422 « Invalid final data counts » malgré une charge utile correcte

Sujets connexes