sorry another quick one. trying to run the example from the metaflow to test is our scheduling would work (after some permission adjustments):

from metaflow import FlowSpec, Parameter, step
 
class SFNTestFlow(FlowSpec):
 
    num = Parameter('num',
                    help="Give a number",
                    default=1)
 
    @step
    def start(self):
        print("The number defined as a parameter is", self.num)
        self.next(self.end)
 
    @step
    def end(self):
        print('done!')
 
if __name__ == '__main__':
    SFNTestFlow()

when I run:

python sfntest.py step-functions create

I get the below. My understanding is that AWS does not like the name? Thanks.

The namespace of this production flow is

production:metaflow-*-55ff636_sfntestflow-0-dmbi*

To analyze results of this production flow add this line in your notebooks:

namespace("production:metaflow-*-55ff636_sfntestflow-0-dmbi")*

If you want to authorize other people to deploy new versions of this flow to AWS Step Functions, they need to call

step-functions create --authorize metaflow-*-55ff636_sfntestflow-0-dmbi*

when deploying this flow to AWS Step Functions for the first time.

See "Organizing Results" at <https://docs.metaflow.org/> for more information about production tokens.

*AWS Step Functions error*:

InvalidName("An error occurred (InvalidName) when calling the CreateStateMachine operation: Invalid Name: 'metaflow-*-55ff636_SFNTestFlow'")*

For argo, you would need to use the

@project

decorator. Perhaps it is the same here.

Thanks I tried this and still get something along those lines: AWS Step Functions error: InvalidName(“An error occurred (InvalidName) when calling the CreateStateMachine operation: Invalid Name: ’metaflow

it seems that your config has an invalid entry -

metaflow-*-55ff636*

?>