Callbacks and long-running operations

Operations that return before they finish are the shape people model wrongly, and the naive version reports success too early. A long-running Fusion operation typically ACCEPTS your request and returns immediately — with an identifier, not a result. The work happens afterwards. The response you got means "received", not "done", and an integration that treats the 200 as completion tells everything downstream that a job succeeded when it has not started. THAT IS THE FAILURE: not an error, a false success. A flow that reports completion, a downstream system that proceeds, and a load that then fails half an hour later with nobody listening. TWO WAYS TO DO IT PROPERLY. POLLING: keep the identifier, and check the status until it reaches a terminal state. Simple, works everywhere, and it costs messages — so poll with a sensible interval and a cap rather than in a tight loop, which is Module…

In this module: Module 4 · The Fusion adapter in depth

1. 1What the Fusion adapter gives you
2. 2Browsing the catalogue
3. 3Business objects versus services
4. 4Subscribing to a business event
5. 5The service account and its roles
6. 6Bulk operations and the file route
7. 7Callbacks and long-running operations
8. 8ERP integration patterns
9. 9Reading a Fusion fault
10. 10Surviving a Fusion quarterly update
11. 11What breaks: five Fusion adapter failures
12. 12Lab briefing · Read and write Fusion from OIC