#MuleSoft Anypoint Platform13 utenti parlano di questo argomento

Hi Jakeer!

Since the schedulers are still executing successfully and the logs are present, this looks more like a CloudHub 2.0 Runtime Manager UI/metadata issue than the scheduler itself being disabled. 

Because it started immediately after a deployment, I’d compare the deployed application configuration between Demo, QA, and Stage, especially the scheduler configuration in the Mule application properties and the deployed artifact.

A few things I’d check:

• Confirm the scheduler flows are still packaged in the deployed artifact.
• Compare the scheduler-related configuration/properties between Demo, QA, and Stage.
• Check whether the deployment changed the application name, environment, or runtime version.
• Redeploy the same artifact/configuration to QA and see whether the schedulers reappear.
• Check Runtime Manager/API responses for the application rather than relying only on the UI. If the scheduler metadata is returned through the API but not displayed in Runtime Manager, that would strongly point to a UI/metadata issue.

Since the jobs are actually running, I’d avoid changing the scheduler configuration just to fix the UI until you confirm whether the schedules are missing from Runtime Manager itself or only from the Scheduler page. 

If you can share the Mule runtime version, deployment method, and whether the QA/Stage deployments use the exact same artifact as Demo, that would help narrow it down. 

Hi @Prashant Jain

 This looks like an onboarding/provisioning issue rather than a tenant-key issue. The error 

“Organization is not yet onboarded to GDoT”

generally means the Salesforce org needs to be provisioned/onboarded before the Anypoint Platform connection can be established.  

Please check with your Salesforce/MuleSoft admin or MuleSoft Support/CSM team to confirm the org's GDoT onboarding status. Once onboarding is completed, retry using the Salesforce Org Tenant Key from Setup → MuleSoft → Anypoint Platform Setup  

https://docs.mulesoft.com/access-management/connecting-salesforce-orgs?utm

 If you find this response helpful, please mark it as the Accepted Answer, as it may also help other Trailblazers.  

Hello @sainath reddy

 MuleSoft Anypoint Platform is used to connect different applications, systems, APIs, and data sources. 

 At a high level, it works like this:

Source System --> MuleSoft --> Target System

For example:

Salesforce --> MuleSoft --> SAP

API Design – Use Anypoint Design Center / API Designer to design and document APIs.

API Development – Build the integration using Anypoint Studio and Mule applications.

Connectors – MuleSoft provides connectors for Salesforce, SAP, databases, HTTP, etc., so systems can communicate without building everything from scratch.

Data Transformation – Use DataWeave to transform data between different formats, such as JSON, XML, and CSV.

API Management – Use API Manager to secure, govern, monitor, and control APIs.

Deployment – Deploy Mule applications to environments such as CloudHub or other supported runtimes.

Monitoring – Use Anypoint Monitoring to monitor applications, APIs, errors, and performance.

Hi @Anindya Chowdhury

I totally agree with you. The vendor's business logic and mapping should be maintained on the vendor's side. 

However, if the vendor requires a service that returns data in the format they expect, I'd suggest offer two endpoints:

1. A standard endpoint that returns the canonical data without any translation (your primary service).
2. A dedicated reference API (experience API) for that specific vendor, which provides the translation between your canonical values and the vendor's requirements.

With this approach, all consumers would use the first endpoint to retrieve the data and the vendor would consume both to get the translation response.

I hope this helps. BRs 

César.

Hi, 

Would it be possible to proceed by mocking the Database Select operation instead? 

Place it in Behavior. 

Hi @Elisabeth Guinard

, 

I'm just checking my notes. I think the schedulers reappeared for me by themselves after a little while. I also found that, although they weren't showing in the UI, the schedulers were still running.

Are you seeing something similar?

Just a couple of questions:

• Are you deploying them using Anypoint Exchange V3?
• Do you have a development environment for the API? If so, are the schedulers visible there?

Kind regards,

Dan