Troubleshooting

Troubleshooting

Even with a simple setup, small mistakes in structure, naming, or usage can lead to errors. This section lists common issues developers encounter when working with the SDK — and how to fix them.

Problem: Error message

Requested script can not be found

Possible causes:

• The endpoint you called, e.g. index.php, does not exist
• The application directory name in the URL doesn't match any actual folder.
• The SDK is not installed in the same directory as the application.

Problem: Error message

Custom application script <app-folder>/<endpoint> does not implement a closure

Possible causes:

• The endpoint you called, e.g. index.php, does not implement a closure

Problem: Error message

No route found for GET http(s)://[jobrouter-url]/custom_applications/<app-folder>/<endpoint>

Possible causes:

• The correct URL path is /custom-applications/ (with a dash), not an underscore.

Problem: Error message

Custom application "<app-folder>/<endpoint>" has unresolvable type for parameter $myInterface

Possible causes:

• You defined an interface for closure parameter $myInterface that does not exist (check for typos)
• You did not define a use statement for the interface assigned to parameter $myInterface
• You forgot to specify the interface for parameter $myInterface (type hint is missing)

General Debugging Tips

• Add temporary echo or var_dump() statements inside the closure to inspect values.
• Catch exceptions and display the error message in the browser for easier diagnosis.
• Log errors using the provided SDK interface