GNP propagation study completion issue

[poza-celona]

Hello,

I’ve run into an issue with GNP project propagation study completion.

Added sites, selected technology for 4G and another run for 5G (separate project) and started propagation for all layers. It appears to runs the propagation study, but never completes it. I’ve run into this previously one or two times, so I signed out, closed browser, restarted, etc. but this time no luck. A different machine as well as a different browser didn’t help.

attached failure screenshot.

The email associated with the GNP is (PII Removed by Staff)           

Any help will be greatly appreciated,

Thanks,

Purak.

[Targul]

Same issues. Started after June 12th from my historical propagation data I ran in my project. Has failed each time since then.

Study type

Received power

Bands

All bands

Generated at

Jun 18, 2024, 10:59 AM

Elapsed

1:47

State

Failed

Error

Flume pipeline failed: generic::permission_denied: RPC (stagepkg) failed for cell 'jf': /BorgMaster.CreatePackage failed -- CLIENT_VIOLATES_BUILD_HORIZON: The binary that sent the RPC is too old. It was built at timestamp 1701786572 and at changelist 587942956. See go/borg-build-horizon-policy for details and fixes. RPC had build_context 'build_changelist: 587942956 build_timestamp: 1701786572 build_target_name: "//spectrum/planner/coverage/pipeline:main" ' and was sent by role spectrum-planner-coverage-pipeline. Binaries talking to Borgmaster must have been built stamped, not earlier than 2023-12-11 10:13:45 (1702318425), and after CL 0. Look in the INFO log for a dump of the failing protocol buffer. See go/borgcfg-logs if you need additional guidance how to find the logs. passed through: ==> dist_proc/dax/workflow/worker_pool_manager/cluster_manager/borg_cluster_manager_api.cc:563; source: coverage.cc:545

[justin-terwee]

I was able to run a propagation on the 14th but same error as you are seeing from then on.

[Alex_S]

Thanks for your patience.

Our engineering team believes they have identified and corrected the source of this issue - you should now be able to re-run coverage in the affected projects.