Hi, having issues with an apify import. appreciate any ideas

Hey Michael- The error there means that the provided actor run or dataset ID couldn't be located. That's usually for one of the following reasons: 1. If the provided task or run actor is incorrect or doesn't exist (due to typo, deletion, etc.). 2. If the Apify actor does not have any runs associated with it, so there's no data to pull in. High level on two approaches: - If a specific task is selected to import from, the table will only be updated with results from that particular run. - If the Apify Actor is selected, without a specific task/run selected, it will pull data from the latest run and all following runs of that actor, daily. If you'd prefer to pull runs from a specific actor and not just one task in your Apify account, this would be the option to go with. (More on actor vs. task: https://help.apify.com/en/articles/4865788-what-is-an-actor https://help.apify.com/en/articles/8403866-what-is-an-actor-task ) Does that help? -Mark

Hi Mark L. unfortunately not. I want it to pull every run from the task, which is scheduled to run weekly. I have set everything up correctly yesterday, but it isn't connecting for some reason, Pls take a look: https://app.clay.com/workspaces/360985/workbooks/wb_ZMYMH7pxAqQZ/tables/t_zK5nyqFcf9TT/views/gv_fFxirqC29BEJ

The tasks are correct, and I was able to connect them properly last night. They're showing this err since this morning.

I just don't understand what I'm doing wrong

I should note all of these tasks have run fresh this morning.

Hey Michael, I just took a look at your table and see you were able to successfully add all the runs from this actor as 11 different sources! What did you end up changing? Additionally, is there anything we can still help with?

Just tried a new one this morning, and it broke again. I think there's an issue between Clay and Apify detecting certain types of tasks. You might want to look into it.

Thanks, Michael. When I was combing through, I noticed that 3 of the sources with errors referred to the same actor/task combo... Apify Task: rRyShcXsgvMobMAxX Apify Actor: gdbRh93zn42kBYDyS ...and naturally returned the same error from Apify ("Actor task was not found"). Could you share more about those? The last was returning "Actor run/ dataset not found." Apify Task: oJlblvJlpjEpULKea Apify Actor: gdbRh93zn42kBYDyS So I'm curious to know more about those jobs, too.