# Default schema is not coupled to pipeline revision

**URL:** <https://community.seqera.io/t/default-schema-is-not-coupled-to-pipeline-revision/226>\
**Category:** Ask for help\
**Tags:** platform, schema\
**Created:** [October 27, 2023, 7:06am UTC](https://community.seqera.io/t/default-schema-is-not-coupled-to-pipeline-revision/226 "2023-10-27T07:06:02Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Johannes\_Alneberg](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/johannes_alneberg/32/241_2.png) [@Johannes\_Alneberg](https://community.seqera.io/u/Johannes_Alneberg)\
**Post date:** [October 27, 2023, 7:06am UTC](https://community.seqera.io/t/default-schema-is-not-coupled-to-pipeline-revision/226/1 "2023-10-27T07:06:02Z")

</div>

Hello!

Running on Seqera platform enterprise version 23.2.0\_d157b0d I was very happy to see the new schema based form for parameters. I was attempting to run a local pipeline with the tower agent. However, the schema was based on the latest revision of the pipeline while I was attempting to run a slightly older revision and some parameters has of course changed between these versions.

I am able to change the pipeline revision after the form has been filled in but then the parameters json is already set up and I would have to manually go in and check all the parameters that could have been affected.

To me it would make perfect sense if the schema based form is loaded after the revision of the pipeline is selected?

I guess workarounds would be to either add a new pipeline where the correct schema is hardcoded or manually edit the affected parameters in the launch settings.

Thank you,  
Johannes

---

_[View the full topic](https://community.seqera.io/t/default-schema-is-not-coupled-to-pipeline-revision/226)._