Temporary Slowness in the “Generating Databases” Step of Daily Deltas

Overview

Sometimes the “Generating databases” step in the Daily Deltas courier group may take longer than usual to complete.
While this step typically finishes within a predictable time window, occasional delays can happen due to temporary system conditions.

This article explains why this slowness may occur, how to assess impact, and what to expect going forward.

Symptoms

You may notice one or more of the following:

  • “Generating databases” runs longer than its normal duration

  • The workflow remains In Progress for several hours

  • Downstream campaigns are delayed while waiting for refreshed data

  • No errors appear, but completion time is higher than expected

Why This Happens

The Generating databases step is resource-intensive and can be affected by:

  • Temporary system load

  • Large data volumes being processed

  • Internal platform resource scheduling

In some cases, even if there are no additional workflows or campaigns running, a one-time spike in system load can cause this step to take longer than usual.

This does not indicate:

  • A configuration issue

  • A data problem

  • A recurring platform bug

What to Check When This Occurs

If you notice this step taking longer than expected:

  1. Confirm progress

    • Check whether databases are actively generating

  2. Wait for completion

    • If the step is still progressing and no errors are shown, it usually completes successfully

  3. Monitor the next run

    • Check if the next scheduled run returns to normal duration

If the delay does not repeat, no action is required.

When to Contact Support

You should reach out to Support if:

  • The delay happens repeatedly across multiple runs

  • The step stalls without making progress

  • Campaigns are consistently impacted

  • The duration keeps increasing over time

Support can then review trends and take further action if needed.

Expected Outcome

In most cases:

  • The delayed run completes successfully

  • Subsequent Daily Deltas runs return to normal timing

  • No long-term impact is observed

A single delayed run is usually considered a one-off performance event.

Best Practices

  • Allow occasional flexibility in campaign schedules for rare delays

  • Monitor trends rather than a single run

  • Avoid restarting workflows unless an error occurs

  • Contact Support only if slowness becomes consistent

Summary

A longer-than-usual “Generating databases” step is often caused by temporary system load and is typically a one-time event.
If the next runs complete within the normal time range, no further action is needed.

Monitoring trends over time helps distinguish between expected variability and real issues.

Applies To

  • Daily Deltas courier group

  • Database generation step

  • Campaigns dependent on refreshed data

  • Workflow performance monitoring