Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Screenshare - 2023-07-22 6:29:03 PM.webm

Hey people, I’m having troubles adding an automation. my deployment flow has only one parameter called “event”, and when I type this happens:

Might have something to do with the formatter? Its impossible for me to add the event as the input of the flow parameter.

Hmm we’ve had this same issue before and fixed it so surprised to see it again. Can you share the schema for your deployment? Can you also let me know if you have the same issue when attempting to run the deployment from the ui? Or is it just happening when creating an automation. 

Hey Craig, the issue happens on Automation UI. The parameters section is not suffering this issue on the textarea.

```###
### A complete description of a Prefect Deployment for flow 'webhook-flow-twilio-inbound'
###
name: twilio_deployment
description: null
version: 43bb017a1f896d27549f2ac800bbf3f2
# The work queue that will handle this deployment's runs
work_queue_name: default
work_pool_name: inbound-sms-workpool
tags: []
parameters: {}
schedule: null
is_schedule_active: null
infra_overrides: {}
infrastructure:
  type: process
  env: {}
  labels: {}
  name: null
  command: null
  stream_output: true
  working_dir: null
  block_type_slug: process
  _block_type_slug: process

###
### DO NOT EDIT BELOW THIS LINE
###
flow_name: webhook-flow-twilio-inbound
manifest_path: null
storage: null
path: /path/to/myproject
entrypoint: orchestration/webhook_flow_twilio_inbound.py:webhook_flow_twilio_inbound
parameter_openapi_schema:
  title: Parameters
  type: object
  properties:
    inbound_event:
      title: inbound_event
      position: 0
  required:
  - inbound_event
  definitions: null
timestamp: '2023-07-22T21:36:52.908516+00:00'
triggers: []```

<@U02F25U8A93> is this what you need or you want me to share the inspect json?

<@U05HUT20MDM> that’ll work. Thank you! I think I know what’s up here. I’ll reply back to this thread when we have a fix in place.

Thanks Craig! thanks for the quick response :slightly_smiling_face:

<@U05HUT20MDM> we just merged a fix for this. That'll go out this week with the next release