Let’s talk Alteryx Copilot. Join the live AMA event to connect with the Alteryx team, ask questions, and hear how others are exploring what Copilot can do. Have Copilot questions? Ask here!
Start Free Trial

Weekly Challenges

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA

Challenge #476: Extract Operational Metrics from Your Workflow Logs

patrick_digan
17 - Castor
17 - Castor
Spoiler
image.png
Randy_Yoder
5 - Atom

Tough but good.

Spoiler
Screenshot 2025-05-27 154810.png
myastarling
11 - Bolide

here's my solution!

Goddenra
8 - Asteroid

Probably used too many apps (definitely when compared to others!) but it gets the right result!

alacoume
9 - Comet

very hard

Erin
11 - Bolide

That was fun.

Spoiler
476.png
aatalai
15 - Aurora

C476

TH
8 - Asteroid

This one is primarily about Regex.

It is one more example of wanting specificity and accuracy in the data request (prompt).

I was able to achieve the final answers with relatively few tools. Took at least that many again to get everything to line up the way that the solution wanted.

I did eventually figure out that Task 1 is asking you to group by the workflow. To be clear here - while you ARE expected to produce one row for each log file it is the case that any aggregation that you do should be grouped by the workflow name rather than by the log file.

Learnings:

Sometimes combining two outputs of the Join tool is really useful before you move on.

Clarifying the desired output *BEFORE* you start can save a lot of time and hassle. 

Sometimes, if you are starting at A and trying to get the correct data out of C and you know that B is 1-1 mapped to C then you can find the C data by using A to get to B. Just be careful because that can cause problems if the data structure changes.

Dhrish
8 - Asteroid

Solution

rmassambane
11 - Bolide

476