Troubleshooting
This section describes common issues and how to resolve them.
Problem: AI endpoint does not work
Possible causes:
-
invalid API key
-
wrong authentication type
-
unsupported model
-
provider account does not have access to the selected model
What to check:
-
verify credentials
-
confirm model availability
-
review endpoint settings
-
test with a simpler configuration
Problem: Action cannot be selected in Pimcore
Possible causes:
-
action was not saved
-
Requestador connection is not working correctly
-
subscription or access issue
What to check:
-
confirm the action exists in Requestador
-
verify Requestador access and synchronization
-
confirm that the environment is connected to the correct Requestador instance
Problem: Action executes but returns no usable result
Possible causes:
-
prompt is too vague
-
required parameters are missing
-
validation script rejects the result
-
transform script produces unexpected output
What to check:
-
review prompts
-
confirm all required inputs are mapped
-
review validation logic
-
review transform logic
-
test with a simpler response format
Problem: Pimcore fields are not populated
Possible causes:
-
response field names do not match
-
target Pimcore fields are incorrect
-
localized field language is wrong
-
transform script changed the response structure
What to check:
-
compare returned field names with response mappings
-
verify target Pimcore fields
-
check language settings
-
confirm the final response structure
Problem: Required input values are missing
Possible causes:
-
Pimcore source fields are empty
-
wrong mapping type selected
-
required parameter not configured correctly
What to check:
-
inspect the source object in Pimcore
-
verify input mapping
-
confirm required settings in both Requestador and Pimcore
Problem: Validation fails
Possible causes:
-
AI output does not match required format
-
missing fields
-
unexpected values
-
catalog mismatch
What to check:
-
simplify the prompt
-
inspect expected schema
-
review validation script logic
-
test the action with known-good sample input
Problem: Wrong language is written
Possible causes:
-
wrong language mapping in Pimcore
-
action returns output for a different target language
-
localized field configuration mismatch
What to check:
-
review language mapping
-
verify action input language
-
confirm target field localization settings
General troubleshooting recommendations
-
start with a minimal test case
-
test one action at a time
-
use small and clear prompts first
-
verify the endpoint before troubleshooting Pimcore mappings
-
verify the action before troubleshooting output mappings
-
make changes step by step