Two production issues I keep seeing in Oracle Integration Cloud projects. In both, the integration shows success while the business outcome is wrong.
Fusion REST pagination: the flow succeeds, but the data is incomplete
It works in testing with a small sample. In production it reads page 1, reports success, and the rest of the records never arrive. A few things that help:
count is the number of items in this response, not the total. Don't treat it as the dataset size.
The server can override your requested limit, so advance the offset using the effective limit, not the one you asked for.
Offset paging isn't automatically ordered. If rows are inserted mid-run, page boundaries shift and you get duplicates and gaps. Use a deterministic orderBy with a unique tie-breaker, where the resource supports it.
Guard against hasMore=true with an empty page. Fail with diagnostics instead of looping on the same offset.
For incremental loads, freeze an upper bound at the start of the run, use a small overlap on the lower bound, and only advance the watermark after a fully successful run. Persist it in a table, not just an OIC variable.
Upsert on the source business key so replays don't create duplicates.
For very large volumes, consider BICC instead of REST paging.
2. Connectivity agent: online, but the integration still fails
An agent group can have up to two instances. For most adapters you can run both active, but File, FTP and MLLP require single-active (second agent is standby).
Two agents on the same VM share the same failure modes, so that isn't real HA. Use separate hosts, and confirm both can reach the same endpoints and file paths.
A second agent doesn't help if both depend on the same proxy, DNS or target. It protects against host or agent failure, not shared outages.
When troubleshooting, work from the connection outward (DNS, firewall, proxy, TLS trust, credentials) and test from the agent host, not your laptop. If only one host fails, compare routes, certs, runtime versions and clock sync.
A timeout doesn't mean the target rolled back. Check the target by business key before resubmitting, or you'll create duplicates.
Test failover with real business transactions, not just green status icons.
The common thread: idempotency, durable checkpoints, and runbooks that say what to verify before a retry.
Curious what others have run into. Has anyone been burned by offset shifting under a live collection, or by a failover test that passed while the actual transactions didn't?