Understanding Write Status API vs Job Logs API

Last updated: March 16, 2026

When working with write operations in the Propexo API, you may encounter situations where the Write Status API and Job Logs API return different statuses for the same operation. This article explains why this can happen and what each API represents.

The Difference Between Write Status and Job Logs

The two APIs serve different purposes:

  • Job Logs API (GET /v1/admin/logs/jobs/{job_id}) - Shows the status of individual job executions

  • Write Status API (GET /v1/admin/write-status/{job_id}) - Shows the overall status of the write request and whether the operation was ultimately successful

Why Statuses May Differ

A write operation may involve multiple jobs and processes. For example, when updating a vendor:

  1. The initial update job may complete successfully (showing "SUCCESS" in Job Logs)

  2. However, additional jobs (like reading in the updated vendor data) may still be pending or stuck in the queue

  3. The Write Status API will remain "PENDING" until all related processes are complete

What to Do When Write Status is Stuck on PENDING

If your write status remains "PENDING" while job logs show "SUCCESS", this typically indicates that a related job is stuck in the processing queue. In such cases:

  1. Contact support with the specific job ID

  2. The support team can identify and resolve queue issues

  3. Once resolved, the write status should update to reflect the final state

Best Practices

For comprehensive monitoring of write operations:

  • Use the Write Status API to determine if your write operation was ultimately successful

  • Use the Job Logs API for detailed debugging and to see individual job execution results

  • If you notice discrepancies between the two APIs, contact support for assistance

For more detailed information about write requests, refer to the write requests documentation.