H Extension as epilogue

Hello,
I have a question please.
Consider the following context:
[myContext]
exten => exten1,1,Noop()
exten => exten2,1,Set(x=10)
exten => exten3,1,dosomethingelse()

Whether exten1 was called, or exten2, or exten3, I want that the next line of code will be (e.g.) Goto(somecontext,someexten,1). I could duplicate same => n,Goto(somecontext,someexten,1) for each exten but I thought of using ‘h’ exten at the end of this context:
exten => h,1,Goto(somecontext,someexten,1)

Is it a good practice to use the ‘h’ extension for this purpose? Or perhaps I’m over-looking some side affects that ‘h’ extension might have (e.g. resetting some var’s or doing things that I don’t expect)?

I would say bad practice.

If you can balance the number of priorities on every path, you can do:

exten => exten1,1,Noop()
exten => exten2,1,Set(x=10)
exten => exten3,1,dosomethingelse()
exten => _.,n, Goto(somecontext,someexten,1)

or arguably more clear as to what you are doing:

exten => exten1,1,Noop()
exten => exten2,s,Set(x=10)
exten => exten3,s,dosomethingelse()
exten => _.,n, Goto(somecontext,someexten,1)