Practical fixes for the most common LD3 situations. LD3 is in beta*, so some states are expected while features mature.
Sources are not being ingested
- Confirm the feed URL or document is reachable and publicly accessible.
- Check the source still carries a valid link and attribution — LD3 will not ingest anonymous sources.
- Re-connect the source; intake is a configuration step and will not run until at least one source or monitored topic exists.
Verification flags a source as conflicting
That is expected behaviour. LD3 flags* low-trust or conflicting sources rather than using them silently. Review the conflict, prefer higher-trust sources, or resolve the contradiction before generation.
A review is stuck in pending
- Assign a reviewer, or escalate to human review.
- If the draft is blocked — missing sources*, supply the cited source before it can proceed.
- If it is blocked — policy or quality*, address the policy or quality note.
A publish job is queued or blocked
- At the default level (L1), external posts wait for an approver. Approve the gate to proceed.
- Confirm the target channel is connected and authorised* — publishing is a configuration step.
- A blocked job may be held by the quality gate; check the review state first.
A channel shows no new posts
- Verify the channel connection in Ottili ONE is still authorised.
- Check the content type's channel strategy — not every story maps to every channel.
- Confirm the publishing level allows the post to go out.
Analytics look delayed
Performance aggregates back to the package and its sources after publish. Allow time for reach and engagement to register; conversion data depends on the connected channels reporting back.
Still stuck?
These guides cover the pipeline end to end. If a state is not described here, contact support from the documentation footer — please include the package or source name so the team can trace it.
Related
- LD3 sources — intake issues.
- LD3 approval gates — publish holds.
Was this article helpful?