# CORS error for server requests [SOLVED]

If you’re doing

```
--cors "*"
```

and still facing the same issue, it’s probably because of the wrong double-quote characters. Please use

```
--cors "*"
```

---

If I understand your question correctly, you have a couple of options:

1. You can specify the utterance used in the collect step with the utter parameter, see more information [here](/content/docs/rasa-pro/concepts/flows#using-a-different-response-key-for-the-collect-step/index.html).
2. You can specify a custom action to generate the collect step utterance. This allows fully dynamic prompting in collect …

---

Hi [@serranomorante](https://forum.rasa.com/u/serranomorante) [@imabhinav-am](https://forum.rasa.com/u/imabhinav-am)’s answer is correct. However if you want to closely observe the verbose output of the separate services (e.g. imagine there comes an NLG server in addition) you might think of a named screen or, the more stable way:

Deploy it as a service that can be started and stopped independently.

---

The Rasa custom action server does not have rasa pro as a dependency, so you’re free to use the most recent version of OpenAI in your custom actions.

---

This should be put inside the documentation for local development using Rasa Pro.