Oracle Private Agent Factory

Overview

Review gateway activity and find details that need attention.

Checking

Messaging overview

Waiting for overview data

Request path

From message to reply

  1. 1Receive & verifyCheck the incoming message and provider signature.
  2. 2Queue the workSave the job and wait for processing.
  3. 3Run PAFSend the request with its conversation context.
  4. 4Deliver the replySend the response through the connected channel.

This explains the message path. It does not show live progress or timing. Open Delivery Logs to inspect recorded requests.

Investigate

Go straight to the details

How conversation context is kept

DIVA stores the PAF room identifier returned for a conversation and reuses it in later messages. Manage channel-to-agent bindings in Connections.

PAF Agents

API keys are encrypted and are never displayed again after saving.

NameEndpointStatusLast testedActions

Manage provider credentials, callbacks, and the PAF agents receiving messages.

Report worker

Rich Message Lab

Test text, media, WhatsApp templates, or LINE Flex messages without invoking PAF.

This sends to a real target. Verify the ID before sending.

PAF Feature Tests

Validate formatting, charts, actions, and technical reports against the PAF agent linked to a Telegram connection. Tests do not send Telegram messages or execute actions.

Delivery Logs

Displays redacted data without storing tokens or Authorization headers.

Flat delivery list

Recorded duration may exclude queue wait and can cover one attempt or several stages. For inbound requests, Queued means received by DIVA. Delivered means the provider accepted the reply.

TimeConnectionRoom IDDirectionStatusMessage previewRecorded durationTrace IDActions