Just to add to this, the whole thing is driven by:

• Managerial type has problem.
• Managerial type sees possible solution (a somewhat naive and eager to help techie).
• Managerial type tries that solution.

That's it: it's all about them and their problem and zero about the person they're asking it from, including about any "learning" (if it was about "learning" it would be a "problem in your area of expertise but more complex that what you've done so far" and even those are commonly a "solve my problem" that just happen to fall in your area if beyond what you've so far done).

So for somebody receiving such "solve me this problem (outside your expertise)" request, the right approach is to make it so that "any problems from me doing this, are not my problems" and make sure it's all on record because sometimes it is actually needed (normally it's not, but plenty of managerial types will blame you if this solution of theirs through using a person with no domain expertise blows up, so one does it "on the record" just in case).

Hence, full-on on the record including a clear notice from your side about your lack of training for the job and with clear explanation of consequences for other projects ("If I'm doing this, I'm not doing that", as said managers might be trying to get you to use your personal time in solving their problem, i.e. you're still expected to do all the rest in addition to solving their problem) and the authorization of the managers of said projects.

It's sad that you need to cover your ass just in case, but if it's all on the up and up said manager has no reason to see your approach in a negative way (it actually looks professional and, had they been managing one of the projects you will put on hold for this request, they would want you to make sure their approval is obtained just like you did), whilst if it is not on the up and up, he or she will give up and seek an easier victim, not just this time but likely from then onwards.

If they do end up getting everything prim and proper and authorized for you to do this totally new kind of thing, you just got yourself a consequences-free and reasonably open-ended chance to play around with new stuff, on the company dole, with no expectations you'll be good at it, so have fun.

Not trying to troll you but technically, that would also preclude being able to expand your skillset since you can only do what you‘re already good at.

Then again, I‘m probably splitting hairs. Thanks for elaborating.

A boring routine, even if it's short, is a distraction from stuff that require more focus. Also it's a source of human errors.

At least that's how I rationalize it ~~because, really, it's just more fun to work on automating stuff~~.

Yeah, I'd be all over something like this. I'd document that I was being asked to do something outside of my wheelhouse, of course, if my boss wants me to spend my time on this then that's on him. But I wouldn't object, sounds like a fun activity.