Tools > IML Functions: "Scenario ID" variable
complete
Dominik Lamacz
I very often reference a scenario by it's ID in email and Slack modules so we know which scenario log we should review in case there is any confusion as to what exactly happened. Currently I do this by using the scenario URL, however in case I create a copy of the scenario, the ID changes and so does the URL. In this case I need to manually edit every email/Slack module which is quite time consuming and not every time do I manage to keep every module on my mind. Adding a scenario ID function would solve this issue.
Photo Viewer
View photos in a modal
Log In
D
Darin Patterson
updated the status to
complete
all features of this idea have been delivered (a long time ago).
akash.paul@integromat.com
Dear Integromates,
We have just released this new feature. Using the variable you would be able to get the scenario ID along with the execution ID.
New global variable -> executionId
It contains the ID of the current execution. Useful for logging and monitoring purposes.
You can use get and split function to get the scenario id from the execution id.
Please, check it out, test it and let us know if it works as expected.
Happy Automating!
Thanks,
The Integromat Team
Photo Viewer
View photos in a modal
Ffern
Can we also add the ‘run ID’? Or even run history URL? Run histories aren’t searchable so it’s difficult to find the exact run (in the run history log) that went wrong if we can’t log it’s ID somewhere...
Michal Máša
A partial workaround: use "Tools > Set variable" module right after the trigger to set a "Scenario ID" variable and use this variable in all the modules referring to the Scenario ID.