Why am I Receiving a 404 Error When Trying to Schedule a Pipedream Workflow with New-Scheduled Tasks Source?

1

This topic was automatically generated from Slack. You can find the original thread here.

other still unreplied/unsolved issue is about new-scheduled tasks source for scheduling pipedream workflow from other pipedream workflow; I did everything as described in documentation, but still getting Error - Request failed with status code 404: {“error”:“record not found”} in the source logs when trying to send http-request to it to create a schedule, wondering if the source itself is not functioning already (last update was loong time ago) - investigated that with pi-bot earlier and came to a conclusion that there is some issue with the source, could you please check & fix that? Would be really helpful

2

or maybe there is some workaround for that for now? it might be really useful feature for me

3

Thanks, I’ll look into this too. Can you tell me more about the use case for triggering scheduled tasks?

4

sorry for the late reply, here is the link to the thread where I tried to solve that with bot, it contains all the details: Slack

5

any updates on that? actually working at the moment (this is pretty urgent for me) on automation that requires this kind of scheduling/unscheduling workflow from another workflow, and now missing this feature because of that

6

yes, I was just talking about this with yesterday and we’re working with the team to address.

Michael — this source also uses the subscriptions API to schedule emits, and I think we also just need to make sure this passes the workspace_id param in the create subscription API request like for the others and it should work.

7

any updates on that?

8

We’re still investigating, and trying to get the root cause. We will keep you posted on this thread!

9

Can you try to create the source again once more? This should be fixed.

10

I created a source and tested with built-in ‘helper’ action that schedules task in X seconds - it worked fine! will write keep you posted, planning to manually write code that uses the /schedule endpoint to see how it works directly from the code, without pre-built ui ‘helpers’ steps

11

glad to hear, thanks