When a C_Period job is defined and started with input parameters, there is no option to view the current parameter assignments that will be used by each period execution. It is unknown and not documented in any of the period container's reports, including the activation report.
This makes it difficult, especially if there are are multiple recurring executions of the same object, each having a different set of input parameters and schedule. Because there may be doubt as to which instance uses which configuration, the user must cancel all active periods and restart them with new parameters to ensure they are aware which are which, but this will become quickly forgotten over time and will be required to reset them again.
Version 24.X and all prior versions
This behavior is currently considered as designed.
Please refer to DE170321 where this request for enhancement has been accepted for a future release, but the release to be used has not been committed at this time. There may be additional news within the next 6 months (by the first calendar quarter of 2026).