Situation

A spatial data team needs Flux to keep processing a recurring VicMap DataShare order, but the order must be closed and recreated in DataShare before Flux can continue using the refreshed order configuration.

Outcome

The team closes the old recurring order, creates the replacement order, confirms the schedule, and leaves Flux with a recurring DataShare order that can be checked, downloaded, imported, and logged by the normal automation path.

Steps

  1. Open the DataShare orders page and find the recurring order that Flux uses.

    DataShare recurring orders list

  2. Open the recurring order details and close the old recurring order when it is no longer the active source for Flux.

    DataShare recurring order details

    DataShare close recurring order action

  3. Reorder from the closed recurring order and apply the order configuration that matches the Flux target.

    DataShare reorder recurring order action

    DataShare apply order configuration

  4. Confirm the recurring schedule, proceed to your details, and confirm the replacement order.

    DataShare weekly recurring schedule

    DataShare proceed to your details

    DataShare confirm order

  5. Let the recurring order move into processing, then return to the Flux automation path that checks orders, downloads updates, imports files, and records logs.

    DataShare recurring order processing

Implementation Evidence

  • Flux/Hive/Hive.Application/DataShare/
  • Flux/PowerShell/DataShare/
  • Docs/Generated/PowerShell/Get-FluxDataShareOrderConfig.mdx
  • Docs/Generated/PowerShell/Get-FluxDataShareOrderReady.mdx