Running provisions via API - naming conventions?

Hello,

anybody noticed that when running a provisions script for a device via API, the name of the provisions script should NOT include underscore (_) in its name?

No error is reported, but script just does NOT run.

By renaming provisions script to NOT include underscore in its name, script runs perfectly.

I am referring to running provisions script via API, example:
POST https://{acs-host}:7557/devices/{device-id}/tasks/?timeout=3&connection_request

with POSTED data:
{“name”:“provisions”,“provisions”:[[“my_script”, “parameter1”, “parameter2”]]}

vs

{“name”:“provisions”,“provisions”:[[“myScript”, “parameter1”, “parameter2”]]}

1st instance does NOT trigger the script, 2nd instance runs script flawlessly.

This issue is not observed when using provision scripts in Presets.

Just my 5 cents. :slight_smile:

Regards,
Robert.