# Unexpected argument error when calling continuation pipeline

**URL:** <https://discuss.circleci.com/t/unexpected-argument-error-when-calling-continuation-pipeline/42355>\
**Category:** Bug Reports\
**Tags:** circle-yml, dynamic-config\
**Created:** [December 22, 2021, 7:42am UTC](https://discuss.circleci.com/t/unexpected-argument-error-when-calling-continuation-pipeline/42355 "2021-12-22T07:42:46Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ralbertazzi](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ralbertazzi/32/30434_2.png) [@ralbertazzi](https://discuss.circleci.com/u/ralbertazzi)\
**Post date:** [June 21, 2022, 6:29pm UTC](https://discuss.circleci.com/t/unexpected-argument-error-when-calling-continuation-pipeline/42355/4 "2022-06-21T18:29:39Z")

</div>

@rit1010 check the solution from [this discussion](https://discuss.circleci.com/t/manually-trigger-path-filtered-workflow/42346/2). Specifically, the `manual-workflow-a` and `manual-workflow-b` parameters have been defined in the continuation config even though they are not even used. Without duplicating them you would get the error “Unexpected argument(s)” highlighted by @kochax

Is this parameter forwarding the expected behaviour or is it a bug? If it’s expected it should be documented

---

_[View the full topic](https://discuss.circleci.com/t/unexpected-argument-error-when-calling-continuation-pipeline/42355)._