Currently, when triggering a publication refresh in Domo, the process must run to completion once started. There is no option to pause, cancel, or abort an in-progress refresh job.
According to Domo documentation, users can initiate and monitor publication refreshes, but there is no control to stop a job once it has started.
This creates challenges in real-world scenarios where:
- Refresh jobs can take a long time depending on the number of datasets, dashboards, and subscribers.
- A refresh may be triggered accidentally or at an inconvenient time.
- Issues are identified mid-refresh (e.g., incorrect content, missing datasets, or configuration errors).
- Users want to avoid unnecessary processing or system load.
Proposed Enhancement
Introduce the ability to:
- Cancel or abort an ongoing publication refresh
- Optionally pause and resume refresh jobs
- Provide clear status feedback when a job is stopped
Business Impact
This enhancement would:
- Improve operational control and flexibility
- Reduce unnecessary compute/resource usage
- Prevent propagation of incorrect or incomplete content to subscriber instances
- Enhance user experience when managing large or complex publications
