Function Release Automate

Hello,

I am trying to create an automation using Speckle Automate and basing it off of one of the functions that were published during the previous Automate phase. I followed the steps, including adding the token and URL of the server, and then committed the changes to GitHub. The changes are saved and I set a release for the function but I am still getting the error that the function needs at least one release to be used in an automation. Nothing I have tried changed that issue. What am I missing?

Thank you.

I’ll look into this now. Was your function initially made using the wizard from a workspace?

My function was initially created using the wizard from a workspace and then edited using Visual Studio and pushed back into GitHub manually.

If you could share the repo and the function record URL with me I can look in more detail - you can send a DM if you prefer

I cannot replicate this error.

The steps I followed:

  1. From a workspace > automations > create new function
  2. Select either template
  3. Follow link to the github repo
  4. Making no code changes, create a release with tag “1st” < can be anything
  5. Action proceeds to deployment

There is no need to make any changes to tokens or server URLs. In case you were pointing the function and hoping to run on your own server, this will not work as Automate is exclusively available to app.speckle.systems from with Workspaces at this time.

I was only on app.speckle.systems. Here is an image of the issue I am facing currently.

This is when I am in the function’s page.

And here when I go to create an Automation immediately, clicking on create does nothing. I will share the repository soon.

And the top half of that screen?

Does it give a Last Published info??

It does not give me last published no matter how many times I’ve created a release, pushed it back to GitHub, or done anything else. I am editing the code on Visual Studio and pushing it back into GitHub before creating the release. It now showed that there has been an error in building the repository so maybe that is it. I will share the repository now to see if there is anything beyond just that error.

Yes. Report any errors in the Action. It’s that which deploys if successfully building the container

I will make sure to check what they are as soon as possible and come back if there is anything worth mentioning.

Hello again.

The Automation now works. The errors were a case of using foreach on an integer (which was fixed). Specifically, this was the error.

foreach statement cannot operate on variables of type ‘int’ because ‘int’ does not contain a public instance or extension definition for ‘GetEnumerator’

It was handled and fixed. My next issue turned out to be in the FunctionInputs struct where the class was not recognized, most likely due to an indent issue. This was also addressed and now the Automation is working.

Thank you for your support.

1 Like

Hello again.

I am running into an issue where the function is reading the parameters but is not reading the fire rating within the parameter variable.
image

The first part shows that the parameter is being read but it will not reach the second part where the Fire Rating is then read. Was there a change in the ID of the fire rating since this code was first written or is it something else?

I should note, in addition, the loop only seems to go to the third section of the data and doesn’t enter the parameters tab. I note that from the ID that gets printed being only the second to last one.

That fire rating example may not have ever worked to completion. I don’t recall there were a spread of fully functional and demonstration only of an idea for a specific dataset.

We’ve removed them for this reason.

We will be publishing soon public functions that are packaged as-is and also documenting example functions for adaptation. Handling revit parameters is certainly going to be part of what we demonstrate but the functions from closed beta, even if they worked a year ago have not been updated to all the SDK changes made since then.

I see. I wanted to make sure of this before continuing. Thank you for the support. We will be continuing using Automate on our end with the information we have been given.