# Connector as Unknown Task in Automation

**URL:** <https://community.tulip.co/t/connector-as-unknown-task-in-automation/14192>\
**Category:** Support, Troubleshooting, & Help\
**Tags:** connectors, automations\
**Created:** [March 20, 2025, 1:47pm UTC](https://community.tulip.co/t/connector-as-unknown-task-in-automation/14192 "2025-03-20T13:47:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bapt.God](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Bapt.God](https://community.tulip.co/u/Bapt.God)\
**Post date:** [March 20, 2025, 1:47pm UTC](https://community.tulip.co/t/connector-as-unknown-task-in-automation/14192/1 "2025-03-20T13:47:29Z")

</div>

Hi 🙂

I am currently facing an issue tryin to run a Connector into an Automation,  
While testing the Automation, the Connector is shown as “Unknown Task”. It looks there is no output neither, which I would like to link to a variable in order to use it later,

 ![Connector issue in Automation](https://us1.discourse-cdn.com/flex020/uploads/agilemfg/original/2X/9/92b7875e06cfc73d3173fb2ec380f2def5d71e20.jpeg)

What could be the issue ? Thanks for your help !!

---

<div class="post-metadata">

**Author:** ![OlgaStroilova](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/olgastroilova/32/7199_2.png) [@OlgaStroilova](https://community.tulip.co/u/OlgaStroilova)\
**Post date:** [March 23, 2025, 2:35pm UTC](https://community.tulip.co/t/connector-as-unknown-task-in-automation/14192/3 "2025-03-23T14:35:30Z")

</div>

Hi @Bapt.God , the “Unknown task” in run history is just a display issue, which is on our radar as a minor UI bug.

From your screenshot, it looks like this automation is failing later due to “Missing record” which means the automation might be trying to get a table record which doesn’t exist.

A first debug step would be to try editing the connector and running it with test input to make sure it works as expected. If that doesn’t work, you might need to reach out to Support to help get at the underlying logs to diagnose which inputs caused missing table records.

We’re working on adding more tracing functionality to make debugging failures like this easier, directly in the Automations UX.