hey team! I have a waterfall that has been stuck on 93-95% for ~2hrs now, i believe i have identified the specific column that's causing the issue (43 rows in awaiting callback); can i stop this specific column so the other ones can run / what should i do? the whole table is only 294 rows, doesnt seem like such a big table to enrich
You can stop the waterfall by clicking the "Stop Updates" button at the bottom right of your screen, then select "Confirm and stop".
For the stuck column with "awaiting callback" status, click the column header and select "Force Rerun Column" to reset it. This should get things moving again without additional charges.
Once you've stopped the waterfall and force-rerun the problematic column, you can restart the enrichment process.
Is that what you were looking for?
wont i get charge again for force re-run column?
No, you won't be charged again for force re-running the column. When you use "Force Rerun Column" to fix stuck enrichments, no additional charges apply for running those rows again.
This feature is specifically designed to help recover stuck processes without extra costs.
Did that answer your question?
If you still need help with managing your waterfall or have any other questions, I’m here to assist. Would you like to provide more details about what you’re trying to resolve?
the stuck column timed out, now im stuck in another column, is there a way to reduce the the time out window?
There isn't a way to adjust the timeout window for columns. When columns get stuck or timeout, the best approach is to use "Force Rerun Column" on the stuck column - click the column header and select that option.
This will reset the column and get it running again without additional charges. You might need to do this for each column that gets stuck as your waterfall progresses.
Does this help?
If you still need help with your waterfall or managing stuck columns, I’m here to assist. Would you like to share more about the issue you’re trying to resolve or any other questions you have?
the table is stuck on >99%, the stop button is greyed out, under force run column in the columns that are still progress there is a token cost listed
When the stop button is greyed out and your table is stuck at >99%, the column is likely in a stuck state.
The token cost showing under "Force Rerun Column" indicates this will charge credits because it's re-running enrichments that consume credits. [1] This is different from stuck columns where force rerun typically doesn't charge - in your case, the columns are still actively processing, not truly stuck.
You'll need to decide if you want to pay the token cost to force rerun those remaining columns, or wait for them to complete naturally.
Is that what you were looking for?
If you still need help with your waterfall or managing the stuck columns, I’m here to assist. Would you like to provide more details about what you’re trying to resolve or any other questions you have?
