My sales team has been using a template for a few months for quick one-off contact searches and it has suddenly stopped working. When they click "Create table using template", the table is created. As soon as they go to add a source, it populates the search result in a new table without the enrichment automations I've set up for them. When they go back to the created template, it does that each time they attempt to add a source. Has something changed about table template use? Or is this a bug?
This sounds like an auto-update setting issue rather than a bug. When you add a source to a table created from a template, the new table might have auto-update disabled at the table level, which would prevent your enrichment automations from running automatically. [1]
The table-level auto-update acts as a master switch - when it's disabled, you have to manually click cells to trigger enrichments, even if individual column auto-update settings are enabled. [2] This could explain why the search results populate but the enrichments don't run.
To fix this, click on the table name to access settings and select "Enable auto-update". You can choose to run existing cells or continue without running them.
Before we dig deeper though, have you tried using Sculptor (the AI tool in the top-right corner) to help rebuild or troubleshoot your template workflow?
If you still need help resolving the issue with your table template and enrichment automations, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific challenges you’re facing?
The search isn't being added to the table, its creating a new one entirely. Auto update is on in the template. The issue is that instead of adding the search on to the table created from the template, an entirely new basic table is being created
This behavior where adding a source creates a new table instead of updating the template-created table isn't covered in our standard troubleshooting docs. When adding a source to an existing table, you need the appropriate columns set up - for example, a "Find company" source requires LinkedIn URLs or Company Domains columns. [1]
Since this is affecting your team's workflow and the standard troubleshooting steps don't address this specific template behavior, I'd recommend trying Sculptor (the AI tool in the top-right corner) first - it can help rebuild or troubleshoot your template workflow and might catch something we're missing.
What type of source are you trying to add to the template-created table, and does the table have the required columns for that source type?
A simple people search, using Name and Company Name. This week is the first week that this issue has come up, no updates have been made to the table or process
This sounds like a specific template behavior issue that's not covered in our standard docs. For a people search using Name and Company Name, you need the right column setup in your template table. [1]
Since this just started happening this week with no changes to your process, and Sculptor might help identify what's changed in your template setup, could you try using Sculptor (the AI tool in the top-right corner) to troubleshoot your template workflow first? Let me know if that helps or if you still see the same behavior where sources create new tables instead of adding to your template.
I tried doing that before reaching out for support
I understand this is frustrating, and I’m routing you to a human agent who can assist you further with this issue.
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

Hi Ali, happy to look into it 💪🏼 could you send the URL link please?
Ali - Sorry for this, it looks 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!
Thank you so much!
Hey- my reps are asking if theres any update yet?
Thanks for following up on this. Our engineering team is continuing to investigate and work toward a fix but we don't have a timeline at this point. We’ll keep this ticket open and update you as we make progress.
