Columns Stuck on Queued After Re-running Clay Workbook Views

Enoch · 2025-01-05 19:15:27.042309+00

Columns stuck as "Queued" even after re-running

Columns Stuck on Queued After Re-running Clay Workbook Views | Clay

10 comments

· Sorted by Oldest

Channeled
APP
·
·
If your columns are stuck in a "Queued" state, try these troubleshooting steps: 1. Force run the columns: • Right-click on the column • Go to "Run Column" > "Force Run All Rows" 2. Check your auto-update settings: • Open table settings • Verify if auto-update is enabled/disabled according to your needs 3. If the issue persists, it could be related to: • Network connection stability • Processing delays due to large data volumes • API quota limitsTry breaking your data into smaller batches and ensure you're within your usage limits for better processing. Sources: Run Options Configuring your table settings | Documentation | Clay University
Channeled
APP
·
·
Hi Enoch! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Stefano
·
·
Hi Enoch, thank you for reaching out. The reason many of the cells are showing as "Queued" is due to our batching process. We process rows in batches, typically executing around 60 rows at a time. Once a batch completes, the next set of rows is processed. This is why you'll see the "Queued" status—these rows are lined up to run next. This is not an error, but simply part of the system's process to handle data efficiently. Depending on the volume of data you're working with, it can take some time for all the rows to be processed, but rest assured the system is working through them as quickly as possible. Let me know if you have any further questions or need assistance with anything else!
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Enoch
·
·
It's still in a "queued" state so I don't think this is normal
Enoch
·
·
bumpin this 🙏
Bo (.
·
·
Hey, thanks for reaching out Enoch - Seems like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more! In the meantime, can you: Duplicate this column > rerun This typically happens when the current column is stopped > re-run > stopped re-run multiple times. Let me know how many credits and I'll add it back! :)
1
Channeled
APP
·
·
Hi Enoch! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
If your columns are stuck in a "Queued" state, try these troubleshooting steps: 1. Force run the columns: • Right-click on the column • Go to "Run Column" > "Force Run All Rows" 2. Check your auto-update settings: • Open table settings • Verify if auto-update is enabled/disabled according to your needs 3. If the issue persists, it could be related to: • Network connection stability • Processing delays due to large data volumes • API quota limitsTry breaking your data into smaller batches and ensure you're within your usage limits for better processing. Sources: Run Options Configuring your table settings | Documentation | Clay University
Channeled
APP
·
·
Hi Enoch! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Stefano
·
·
Hi Enoch, thank you for reaching out. The reason many of the cells are showing as "Queued" is due to our batching process. We process rows in batches, typically executing around 60 rows at a time. Once a batch completes, the next set of rows is processed. This is why you'll see the "Queued" status—these rows are lined up to run next. This is not an error, but simply part of the system's process to handle data efficiently. Depending on the volume of data you're working with, it can take some time for all the rows to be processed, but rest assured the system is working through them as quickly as possible. Let me know if you have any further questions or need assistance with anything else!
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Enoch
·
·
It's still in a "queued" state so I don't think this is normal
Enoch
·
·
bumpin this 🙏
Bo (.
·
·
Hey, thanks for reaching out Enoch - Seems like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more! In the meantime, can you: Duplicate this column > rerun This typically happens when the current column is stopped > re-run > stopped re-run multiple times. Let me know how many credits and I'll add it back! :)
1
Channeled
APP
·
·
Hi Enoch! This thread was recently closed by our Support team. If you have a moment, please share your feedback: