How to Use Priority Push for Faster Processing

TL;DR

Use the --priority-push flag to prioritize your OAA payload in Veza’s processing queue for faster results.

What is Priority Push?

When you push data to Veza, it enters a processing queue. By default, pushes are processed in order. The --priority-push flag moves your push to the front of the queue, so Veza processes it sooner.

Important notes:

  • Priority push does NOT override data from other sources or affect source of truth settings—it only affects processing order.

  • Any data processing already in progress will complete before your priority push item is picked up. Priority push moves you to the front of the waiting queue, not ahead of active processing.

When to Use Priority Push

  • Testing and development — See your changes reflected quickly without waiting

  • Debugging — Verify your integration works without queue delays

  • Urgent updates — When you need data processed as soon as possible

  • Demo environments — Show results to stakeholders without waiting

Basic Usage

uv tool run --from oaa-runner oaa app run \
  --config=config.yaml \
  --save-json \
  --priority-push

Combined with Other Flags

With Debug Output

uv tool run --from oaa-runner oaa app run \
  --config=config.yaml \
  --save-json \
  --priority-push \
  --debug

With External Dependencies

If your integration has a requirements.txt:

uv tool run --with-requirements=requirements.txt --from oaa-runner \
  oaa app run \
  --config=config.yaml \
  --save-json \
  --priority-push

Verifying Priority Push

After running with --priority-push, check the Veza UI:

  1. Navigate to your Provider

  2. Check the Data Source’s last updated timestamp

  3. Verify entities appear as expected

The push should be processed faster than a standard push, though any currently-processing jobs will complete first.

Common Misconceptions

Misconception

Reality

Priority push overrides other data

No — it only affects queue order

Priority push sets source of truth

No — source of truth is configured separately in Veza

Priority push interrupts active processing

No — active jobs complete first; priority push goes to front of waiting queue

Priority push is required for testing

No — it just makes testing faster