Ask Your Question

Does Autofix topology work automatically?

asked 2020-05-10 23:45:44 -0500

uzumaki gravatar image

I created a topology with two pipelines - one creating the dataset, other consuming it. It worked perfectly until one of the pipeline was updated to a newer version.

No indication on the dashboard that this needs to be updated until I actually went to investigate because the record counts obviously were wrong. I go on to the topology and it gives me an option to "Autofix". Anyway, "Autofix" option just creates a glitchy situation where the popup goes into some infinite recursion trying to fix it.

Any ideas how to deal with this situation? I realize creating a new topology would probably be the fastest resolution. Looking for something better.

Tried adding the screenshot. Turns out I don't have enough points for that.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2020-05-12 12:03:40 -0500

iamontheinet gravatar image


Short answer is -- yes, "Autofix" should and usually does fix the issue(s), but you might have run into an edge case. If this is something that's reproducible in your environment, I'd suggest that you reach out to our support team. They'll be able to help and guide you through in a timely manner.

Cheers, Dash

edit flag offensive delete link more


Thanks for your input, Dash. Honestly, I think this would be one of the simplest example of a topology. Anyway, I'll get in touch with the support team. Will update here if I get any solution.

uzumaki gravatar imageuzumaki ( 2020-05-13 23:30:25 -0500 )edit

Sounds good. I am sure there's something unique about your situation because I use topologies often and using "Autofix" feature after updating jobs works as expected.

iamontheinet gravatar imageiamontheinet ( 2020-05-13 23:58:41 -0500 )edit
Login/Signup to Answer

Question Tools

1 follower


Asked: 2020-05-10 23:45:44 -0500

Seen: 32 times

Last updated: May 12