MuleSoft Feed

Hi Stephanie, 

A few things that might help, since

's own channels. 

1. Why you're getting bounced back on Support 

The

Support/Case portal is only available to Professional or Enterprise paid subscribers. If you're on the Free tier, submitting a case there will redirect you, since free users are directed to the Community Forums instead of direct support tickets. That's likely why you keep getting sent back to the home page. 

2. Alternative way to reach them 

If the in-app Help Center login loop won't let you submit a ticket, you can email them directly instead:

This bypasses the portal login issue entirely. 

3. On the login-loop / repeated failures 

Since you've already cleared cache, tried incognito, and different browsers, a few other things worth checking with your Salesforce Admin (if you're not the Admin yourself): 

   - Setup > Connected Apps OAuth Usage — check if

shows a "Blocked" status with an "Unblock" button next to it. If so, it needs to be unblocked there. 

   - Check if your Profile has "Enforce Canvas UI" enabled under Settings > User Profile — if so, you may only be able to log in through the embedded canvas app inside Salesforce, not the standalone

website. 

   - Confirm there are no IP restrictions on your Profile blocking

's published IP addresses. 

   - Confirm "API Enabled" is checked on your Profile under Administrative Permissions. 

4. If uploads keep failing (not just login) 

Since you mentioned it's taking 20-30 attempts to get an upload through, and not just login issues, this could also be an intermittent platform issue on

's status/community forums to see if others are reporting the same thing around the same dates — that'll tell you if it's a known outage versus something specific to your org's setup. 

Given the support portal limitation, the email route (

Greetings, @Nate Schaufler

From the outside looking in, it looks like you have all the required fields. Can you do the following to confirm that you are not missing anything: 

1. Export one working EventRelation record (from an event that already has a contact) 

I suspect you might have to use TRUE & FALSE instead of 1 & 0. 

Be well- 

Katende 

Use Data Loader → Export → EventRelation 

Export fields: EventId, RelationId, IsInvitee, IsParent 

This lets you see the correct structure and flag values.

Hi @Richard Muhumuza

Please refer to the below link - 

https://www.youtube.com/watch?v=-2OS6QylZQ0

If you are targetting to upload files under any specific record - mention the same under FirstPublishLocationId. 

If you want the files to be uploaded under the Salesforce Files - give your user Id under  FirstPublishLocationId.  

You can try with workbench by omitting the ContentDocumentId field - works this way too

 The best way to retain tracking fields like CorrelationId while using a time-based aggregator and aggregator listener in MuleSoft is to explicitly persist and propagate the value as part of the aggregated payload or metadata, rather than relying on flow variables alone (since they are not automatically preserved across aggregation boundaries). Typically, you should include the CorrelationId in the message payload, attributes, or as a custom object before aggregation, and configure the aggregator to group based on that CorrelationId. When the aggregator completes, ensure the aggregated result still contains this field so that the aggregator listener can access it. A common and reliable approach is to store the CorrelationId in an Object Store or external persistence if needed for long-running aggregations, and always map it back into the final message structure, ensuring end-to-end traceability across asynchronous processing. 

Hello, 

Please try the below dataweave.  

%dw 2.0

output application/java

---

"[Booking Loca] in (" ++

((payload[0]."Booking Loca" map ("'" ++ ($ replace "'" with "''") ++ "'")) joinBy ",")

++ ")" 

Thanks!

Data Loader does not require a System Administrator profile.

Any user can use Data Loader as long as:

•  They have the appropriate Salesforce permissions (such as API Enabled). 
•  Their profile or permission sets grant the necessary object-level permissions (Read, Create, Edit, Delete, etc.). 

Object restrictions: Yes, a user can be restricted to specific objects. Data Loader only allows operations on objects for which the user has the required permissions.

Record restrictions: Yes, record-level security still applies. Data Loader respects:

•  Organization-Wide Defaults (OWD) 
•  Role Hierarchy 
•  Sharing Rules 
•  Manual Sharing 
•  Teams/Territories (where applicable) 

Therefore, a non-admin user can use Data Loader, but they will only be able to access and modify the objects and records that their Salesforce permissions and sharing settings allow.

Note: Some Data Loader operations (for example, exporting all records using special permissions such as "View All Data" or modifying records they do not normally have access to) require additional permissions that are typically assigned to administrators.