Campaign queued versus scheduled: identify where a send is waiting

Define the decision

Use a small event timeline to locate the delay. If no job was created, investigate eligibility and scheduling. If a job exists but is not processed, investigate the worker. If processing occurred, inspect the send outcome and rescheduling reason. Jumping directly to a provider complaint can waste time when the message never reached that stage.

Work through the procedure

1. Pick one enrollment and note its next due timestamp, active state and remaining step.
2. Ask the service operator to correlate it with queue and worker evidence if those details are not exposed in the application.
3. Classify the most recent outcome as waiting, rescheduled, rejected, accepted or uncertain. Preserve the original error text with sensitive values redacted.
4. Choose the fix for that stage: schedule correction, worker recovery, capacity wait, credential repair or reconciliation. Avoid applying all fixes at once.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Event ladder
09:00 due
09:01 job processed
09:01 capacity check deferred work
Later next eligible time recorded
Conclusion: worker activity exists; delivery has not yet been attempted
Next action: verify the capacity constraint

Read the result

The example explains why 'the worker is running' and 'my contact has not received mail' can both be true. A process can successfully decide not to send yet. Similarly, a provider acceptance event is stronger evidence than a queued job but still does not establish inbox placement or human reading.

Check before moving on

1. Keep the same enrollment and step identifier throughout the investigation.
2. Compare timestamps in one timezone to avoid inventing gaps from display differences.
3. After a repair, verify a new outcome for the affected job rather than relying solely on service uptime.

Limits and next action

Do not manually enqueue duplicate jobs to test a vague delay. Zintara has eligibility checks and attempt tracking, but operator shortcuts can complicate diagnosis. An uncertain attempt requires reconciliation with provider evidence before any decision to resend the same message.

Source: Zintara sequence product context