David Elliott
08/17/2022, 5:05 PMprefect.exceptions.ClientError: [{'path': ['register_edges'], 'message': 'Edges could not be registered - some edges reference tasks that do not exist within this flow.', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]
however that’s 100% not true - we’ve validated this locally, and all the edges + nodes do exist, which makes me think Prefect Cloud is stopping at 2500 tasks somewhere, and then the edges are throwing an errorecf1e74b-ff7b-43f2-b734-c062084a6c3b
in case you can see anything in the registration logs?Zanie
08/17/2022, 5:31 PMDavid Elliott
08/17/2022, 5:32 PMZanie
08/17/2022, 5:40 PMDavid Elliott
08/17/2022, 5:41 PMZanie
08/17/2022, 5:45 PMlen(serialized_tasks)
is the number you expect and that stop
at L925 after the loop completes is greater than that number we should be able to eliminate a client-side issueDavid Elliott
08/17/2022, 7:13 PMserialized_tasks
and serialized_edges
out to json files, and have since read them into the console and ran a simple comparison to ensure all the edge slugs in the serialized_edges
exist within serialized_tasks
, and they do, so I’m certain there’s something going on with the graphQL not actually registering these tasks or something 🤔
Can you see anything from the cloud logs on your side?Zach Angell
08/17/2022, 9:00 PMDavid Elliott
08/17/2022, 9:14 PMDanny Jones
08/18/2022, 8:50 AMZanie
08/18/2022, 2:08 PMDanny Jones
08/18/2022, 2:11 PM