Use the original service, its provider state and PD AWS Neptune’s Activity together when provisioning appears unfinished. A billing record, an accepted operation and a usable database describe different stages. Neptune provisioning creates a cluster and a compute instance, so a cluster record alone does not establish application readiness.

Find the recorded request

1. Open PD Modules → PD AWS Neptune → Clients & Databases.
2. Identify the original service and intended AWS region.
3. Open Activity and match the service reference and action time.
4. Read the operation, status and redacted result before asking for another change.

Activity is recent history, not a complete audit archive. No matching recent entry does not prove that an earlier request never reached AWS. Compare the original operation with the cluster and member-instance state in your own AWS account before requesting another creation. Record any disagreement between AWS and the module; an absent recent entry is not evidence that no resource exists.

Check what is still pending

Queued or in-progress work needs processing. A Done entry can mean AWS accepted the request while the cluster or instance is still being created or changed. Check the resulting state and private connection path before telling the customer the database is ready.

Check paid-pending-services automation, applicable client-group settings and the running cron. Staff activating a pending service must use the module if a cluster should be created. Payment alone does not prove provider readiness.

See the PD AWS Neptune Blesta guide for related tasks, or explore PD AWS Neptune.