We are experiencing some weird new problems with variables sometimes not being properly replaced during runbook runs.
A few facts:
We are running the latest and greatest version 2021.2 (Build 7428)
We do have 3 workers running
We do have 2 spaces. The project in question was created when there was only 1 space.
The part of the variable not being properly replaced stems from a variable template in a variable set.
The runbook run ist tenanted.
The Runbook run is meant to be trigger by a scheduled trigger every couple of minutes
Most of the time when the runbook run was triggered by a scheduled trigger, the variable replacement fails. But sometimes it does work.
Most of the time when a failed runbook run is triggered again by a human (via âtry againâ), the variable replacement does work and the runbook runs to completion successfully. But sometime it doesnât.
We are not sure when the problem started. It could have emerged this morning after the update to version 2021.2 (Build 7428), but we have no proof.
We donât know how to tackle this one. Please help.
Can you please tell me where the problem variable resides(just confirming the variable is in a library variable set and attached to the project), how it is scoped, and how itâs used within the process? Please let me know if thereâs anything else that differs with the linked issue and what youâre experiencing. If youâd like to send me screenshots of everything in a DM, that would be likely help our reproduction efforts.
Hi!
Any news on this one?
We use this feature for many tasks which run on a daily, hourly basis or even shorter intervals.
Our current workaround is to have one powershell script with a collection of tenant variables and loop over this collection in order to process a specific task for every tenant.
But your feature to have a single trigger with a set of about 20 tenants and let octopus retrieve each tenats variables is currently useless.
The loop works well for tasks with just 1 variable like the tenant name, but we have some database tasks which require more than just one parameter to be substituted.
We need to know if we should develop our own C# solution outside OctopusDeploy (we donât want to go this route) or if you are going to solve this issue soon.
Unfortunately, this isnt something theyâre actively working on yet. They suggest continuing using the workaround for now. In your case, since the workaround isnât great for you, it may be worth it to develop the C# script you referenced earlier if thatâs not a huge undertaking.
Iâm sorry I didnât have better news for you but please feel free to let me know if you have any other questions or concerns.
Hi Jeremy,
being able to use variables in a trigger in a runbook is a key feature, donât you think?
This features ist just broken and should be fixed.
It worked well with 2021.1.7316 and stopped with 7428.
Kind regards
Michael MĂźller
The fix for this should be going out next week if all goes to plan, so please keep an eye on that GitHub issue to see which version you can upgrade to for the fix.
Please let me know if you have any other questions or concerns.
Hi Jeremy,
we installed the update to v2021.2 Build 7808 without problem.
We activated the original triggers which were not using the work around and they work again as intended.