Since we are no longer seeing issue ,Marking this resolved.
We are continuing to monitor for any further issues.
All balances have now been successfully and accurately updated.
We are still monitoring the job ,will keep you posted here.
The rerun has been progressing without any errors since it was initiated. Our team is actively monitoring the job, and we'll promptly share any further updates as they become available.
Job is running without any issue as of now, we are actively monitoring and will keep posting status here.
B.O.D. Job failed due to timeout , Job is rerunning . We will keep you posted for updates.
We have identified the issue with resources on the node and it has been rectified. BOD process is running. ETA is 90 Mins by now.
BOD process is running: The resource constraint issues have been resolved, and the Beginning-of-Day (BOD) process is now running.
Estimated time: The estimated completion time is 2 hours from now
The BOD process delay is caused by a GoBroker BOD pod being stuck in a Pending state due to resource constraints.
This is not a system outage. The engineering team is actively investigating the underlying resource and node scheduling issue.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 5850 services available
Integrations with