Workato · On-prem agent
No profile found (Kafka on-prem)
"No profile found" means the on-prem agent cannot locate the Kafka profile named in the connection when the job runs. It is usually a config.yml mismatch, so check the kafka block, the profile name and the indentation.
VerifiedLast verified
01Error text
No profile found02Likely causes
- The on-prem agent cannot locate the specified Kafka profile at execution. This usually comes from a mismatch in
config.yml.
03How to fix it
Check that the
kafka:block exists inconfig.yml.Check that the profile name matches the connection exactly, including capitalization.
Check that the profile is nested under
kafka:with correct indentation, for example:kafka: myKafkaProfile: bootstrap.servers: "localhost:9092"Restart the agent and rerun the job.
04Official documentation
→Related errors
- Long query error: Missing files profileThis on-prem error means the On-prem files connection and the database connection in the recipe use different on-prem groups. Set both connections to use agents in the same on-prem group.
- Failed to start SDK extension. 520 Connection FailedThis error means the SDK handshake between an on-prem extension and the Workato platform failed during startup. Build the extension with JDK 8 and make sure its post() URLs use the correct port.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Workato work:Open Workato jobsWorkato rates and salariesHire a senior Workato developer